planner: convert cartesian semi join with other nulleq condition to cross semi join with equal condition

[hawkingrei]

What problem does this PR solve?

Issue Number: close #57583
Problem Summary:

What changed and how does it work?

when to convert the equal condition， We only consider the equality condition. but nulleq is considered，too.

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.

convert cartesian semi join with other nulleq condition to cross semi join with equal condition

将具有 nulleq 条件的cartesian semi join  转换为具有相等条件的 semi join 

[hawkingrei]

/test all

[hawkingrei]

/retest

[hawkingrei]

/retest

[hawkingrei]

/retest

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.0601%. Comparing base (cea46f1) to head (8d112ff).
Report is 281 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58075        +/-   ##
================================================
+ Coverage   73.2259%   75.0601%   +1.8341%     
================================================
  Files          1675       1724        +49     
  Lines        462254     470664      +8410     
================================================
+ Hits         338490     353281     +14791     
+ Misses       102989      95249      -7740     
- Partials      20775      22134      +1359     

Flag	Coverage Δ
integration	49.0847% <100.0000%> (?)
unit	72.4491% <100.0000%> (+0.0784%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	61.6605% <ø> (+15.6224%)	⬆️

[hawkingrei]

/retest

[hawkingrei]

/check-issue-triage-complete

[AilinKid]

can you explain why the original positive case normally work even without this fix

mysql> explain select id from t1 intersect select id from t1;
+------------------------------+----------+-----------+---------------+-------------------------------------------------------------+
| id                           | estRows  | task      | access object | operator info                                               |
+------------------------------+----------+-----------+---------------+-------------------------------------------------------------+
| HashJoin_7                   | 6400.00  | root      |               | semi join, equal:[nulleq(test.t1.id, test.t1.id)]           |
| ├─TableReader_18(Build)      | 10000.00 | root      |               | data:TableFullScan_17                                       |
| │ └─TableFullScan_17         | 10000.00 | cop[tikv] | table:t1      | keep order:false, stats:pseudo                              |
| └─HashAgg_12(Probe)          | 8000.00  | root      |               | group by:test.t1.id, funcs:firstrow(test.t1.id)->test.t1.id |
|   └─TableReader_13           | 8000.00  | root      |               | data:HashAgg_8                                              |
|     └─HashAgg_8              | 8000.00  | cop[tikv] |               | group by:test.t1.id,                                        |
|       └─TableFullScan_11     | 10000.00 | cop[tikv] | table:t1      | keep order:false, stats:pseudo                              |
+------------------------------+----------+-----------+---------------+-------------------------------------------------------------+

[hawkingrei]

/retest

[hawkingrei]

explain select id from t1 intersect select id from t1;

it is in this code. In fact, it cannot deduce the elements that can be PredicatePushDown, so the modification point is not triggered.

[hawkingrei]

can you explain why the original positive case normally work even without this fix

mysql> explain select id from t1 intersect select id from t1;
+------------------------------+----------+-----------+---------------+-------------------------------------------------------------+
| id                           | estRows  | task      | access object | operator info                                               |
+------------------------------+----------+-----------+---------------+-------------------------------------------------------------+
| HashJoin_7                   | 6400.00  | root      |               | semi join, equal:[nulleq(test.t1.id, test.t1.id)]           |
| ├─TableReader_18(Build)      | 10000.00 | root      |               | data:TableFullScan_17                                       |
| │ └─TableFullScan_17         | 10000.00 | cop[tikv] | table:t1      | keep order:false, stats:pseudo                              |
| └─HashAgg_12(Probe)          | 8000.00  | root      |               | group by:test.t1.id, funcs:firstrow(test.t1.id)->test.t1.id |
|   └─TableReader_13           | 8000.00  | root      |               | data:HashAgg_8                                              |
|     └─HashAgg_8              | 8000.00  | cop[tikv] |               | group by:test.t1.id,                                        |
|       └─TableFullScan_11     | 10000.00 | cop[tikv] | table:t1      | keep order:false, stats:pseudo                              |
+------------------------------+----------+-----------+---------------+-------------------------------------------------------------+

In fact, it skipes the PredicatePushDown rules when to build logical plan.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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,winoros]
• pkg/planner/OWNERS [AilinKid,winoros]

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-12-16 04:21:40.990116531 +0000 UTC m=+844291.078919059: ☑️ agreed by AilinKid.
• 2024-12-16 09:46:24.534096184 +0000 UTC m=+863774.622898726: ☑️ agreed by winoros.

[hawkingrei]

/cherrypick release-8.5

[ti-chi-bot]

@hawkingrei: new pull request created to branch release-8.5: #58521.

In response to this:

/cherrypick release-8.5

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: #59177.