planner: fix the issue about simplify outer join to inner join | tidb-test=pr/2313

[winoros]

What problem does this PR solve?

Issue Number: close #51560

Problem Summary:

The original codes will push the predicates that are not related to that child.

What changed and how does it work?

Don't do the recursively. Let the predicate-push-down to do the recursively.

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.

None

[codecov]

Codecov Report

Merging #51750 (f629178) into master (47a990e) will decrease coverage by 15.4756%.
Report is 49 commits behind head on master.
The diff coverage is n/a.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #51750         +/-   ##
=================================================
- Coverage   70.7663%   55.2908%   -15.4756%     
=================================================
  Files          1475       1582        +107     
  Lines        437315     612221     +174906     
=================================================
+ Hits         309472     338502      +29030     
- Misses       108511     250780     +142269     
- Partials      19332      22939       +3607     

Flag	Coverage Δ
integration	37.7489% <ø> (?)
unit	70.4928% <ø> (-0.0948%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	51.5643% <ø> (+5.6225%)	⬆️

[winoros]

/retest

[elsa0520]

LGTM

[winoros]

/hold to avoid that tidb side is merged but tidb-test is not.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elsa0520, time-and-fate

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 [elsa0520,time-and-fate]

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-03-14 14:25:16.967345974 +0000 UTC m=+954743.989592363: ☑️ agreed by elsa0520.
• 2024-03-14 16:28:57.334955956 +0000 UTC m=+962164.357202343: ☑️ agreed by time-and-fate.

[winoros]

/unhold

[winoros]

/merge

[ti-chi-bot]

@winoros: We have migrated to builtin LGTM and approve plugins for reviewing.

Please use /approve when you want approve this pull request.

The changes announcement: LGTM plugin changes

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 ti-community-infra/tichi repository.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #52057.

[winoros]

/run-cherry-picker release-7.1

[winoros]

/run-cherry-picker release-7.5

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #52078.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #52079.

[elsa0520]

/cherry-pick release-6.5-20230625-v6.5.3

[ti-chi-bot]

@elsa0520: new pull request created to branch release-6.5-20230625-v6.5.3: #53099.

In response to this:

/cherry-pick release-6.5-20230625-v6.5.3

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 ti-community-infra/tichi repository.