planner, CTE, view: Fix default inline CTE which contains orderby/limit/distinct and inside of view | tidb-test=e1d0c1e615f749e7139f5be95bc4a2b8cedb7380 (#56609)

[ti-chi-bot]

This is an automated cherry-pick of #56609

What problem does this PR solve?

Issue Number: close #56603, close #56582

Problem Summary:

What changed and how does it work?

1. If the CTE contain orderby/limit/distinct and CTE is referenced by another CTE recursive part, it cannot be inlined . Related issue Parsing CTE error with "doesn't yet support 'ORDER BY / LIMIT / SELECT DISTINCT in recursive query block" #56603
2. If the CTE inside of view, the consumerCount of CTE cannot be updated because the view skip the preprocessor phase in during optimizer, it also cannot judge the inline or not. So the CTE inside of view will always be not inlined. Related issue The CTE inside of view can't determine whether it can be inlined #56582

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

修复错误的 inline CTE，如果 CTE 包含 orderby/limit/distinct 子句并且被另外一个 CTE 的 recursive part 所引用。
同时去除对 view 中的 CTE 进行是否默认 inline 的优化。

[elsa0520]

/test mysql-test

[elsa0520]

/test unit-test

[tiprow]

@elsa0520: No presubmit jobs available for pingcap/tidb@release-6.5-20241009-v6.5.10

In response to this:

/test mysql-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tiprow]

@elsa0520: No presubmit jobs available for pingcap/tidb@release-6.5-20241009-v6.5.10

In response to this:

/test unit-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[elsa0520]

/test mysql-test

[tiprow]

@elsa0520: No presubmit jobs available for pingcap/tidb@release-6.5-20241009-v6.5.10

In response to this:

/test mysql-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[elsa0520]

/test mysql-test

[tiprow]

@elsa0520: No presubmit jobs available for pingcap/tidb@release-6.5-20241009-v6.5.10

In response to this:

/test mysql-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[elsa0520]

/test mysql-test

[tiprow]

@elsa0520: No presubmit jobs available for pingcap/tidb@release-6.5-20241009-v6.5.10

In response to this:

/test mysql-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[elsa0520]

/test mysql-test

[tiprow]

@elsa0520: No presubmit jobs available for pingcap/tidb@release-6.5-20241009-v6.5.10

In response to this:

/test mysql-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[elsa0520]

/test mysql-test

[tiprow]

@elsa0520: No presubmit jobs available for pingcap/tidb@release-6.5-20241009-v6.5.10

In response to this:

/test mysql-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

Attention: Patch coverage is 96.29630% with 1 line in your changes missing coverage. Please review.

Please upload report for BASE (release-6.5-20241009-v6.5.10@3635e94). Learn more about missing BASE report.

Additional details and impacted files

@@                        Coverage Diff                        @@
##             release-6.5-20241009-v6.5.10     #56666   +/-   ##
=================================================================
  Coverage                                ?   73.6553%           
=================================================================
  Files                                   ?       1096           
  Lines                                   ?     352276           
  Branches                                ?          0           
=================================================================
  Hits                                    ?     259470           
  Misses                                  ?      76129           
  Partials                                ?      16677           

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, qw4990

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [AilinKid,qw4990]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-10-16 06:13:02.079874787 +0000 UTC m=+424379.228784611: ☑️ agreed by AilinKid.
• 2024-10-16 06:20:19.49560583 +0000 UTC m=+424816.644515662: ☑️ agreed by qw4990.