planner: add projections to keep join keys as col=col

[qw4990]

What problem does this PR solve?

Issue Number: close #46556

Problem Summary: planner: add projections to keep join keys as col=col

What changed and how does it work?

In some cases, after creating new EQ function, the 2 args might not be column anymore, which breaks the assumption that join eq keys must be col=col, to handle this, inject 2 projections.

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

[tiprow]

Hi @qw4990. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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/test-infra repository.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.9319%. Comparing base (5333ac3) to head (8b3ce50).
Report is 12 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #52989         +/-   ##
=================================================
- Coverage   72.3746%   55.9319%   -16.4428%     
=================================================
  Files          1482       1614        +132     
  Lines        428762     605243     +176481     
=================================================
+ Hits         310315     338524      +28209     
- Misses        99149     243441     +144292     
- Partials      19298      23278       +3980     

Flag	Coverage Δ
integration	37.1360% <21.7391%> (?)
unit	70.9568% <100.0000%> (-0.2535%)	⬇️

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

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

[elsa0520]

What is SF means ? Scalar Function ?

[elsa0520]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• pkg/planner/OWNERS [AilinKid,elsa0520]

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-04-30 06:53:41.505572301 +0000 UTC m=+340175.262707872: ☑️ agreed by elsa0520.
• 2024-04-30 08:39:48.397003979 +0000 UTC m=+346542.154139553: ☑️ agreed by AilinKid.

[hawkingrei]

/retest

[qw4990]

/retest

[qw4990]

/cherry-pick release-8.1

[ti-chi-bot]

@qw4990: new pull request created to branch release-8.1: #53326.

In response to this:

/cherry-pick release-8.1

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.