planner: fix panic when the join key is scalarFunction (#30002)

[ti-srebot]

cherry-pick #30002 to release-5.0
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/30778

After apply modifications, you can push your change to this PR via:

git push [email protected]:ti-srebot/tidb.git pr/30778:release-5.0-05ccb8a206da

---

Signed-off-by: yisaer [email protected]

What problem does this PR solve?

Issue Number: close #29401

Problem Summary:

If one side of the join key is string, and the another is json, the expression of the string would be cast to json and marked ParseToJSONFlag which will let WrapWithCastAsJSON wrap extra cast function.

In order to avoid this problem, we remove ParseToJSONFlag temporary during updateEQCond.

The final explain info result for the original issue is like following:

mysql> explain select /*+ inl_hash_join(t1) */ * from t t1 join t t2 on t1.b=t2.e;
+-----------------------------+----------+-----------+---------------+---------------------------------------------------------------------------------------------------------------+
| id                          | estRows  | task      | access object | operator info                                                                                                 |
+-----------------------------+----------+-----------+---------------+---------------------------------------------------------------------------------------------------------------+
| HashJoin_8                  | 12500.00 | root      |               | inner join, equal:[eq(Column#15, test.t.e)]                                                                   |
| ├─TableReader_14(Build)     | 10000.00 | root      |               | data:TableFullScan_13                                                                                         |
| │ └─TableFullScan_13        | 10000.00 | cop[tikv] | table:t2      | keep order:false, stats:pseudo                                                                                |
| └─Projection_10(Probe)      | 10000.00 | root      |               | test.t.id, test.t.a, test.t.b, test.t.c, test.t.d, test.t.e, test.t.f, cast(test.t.b, json BINARY)->Column#15 |
|   └─TableReader_12          | 10000.00 | root      |               | data:TableFullScan_11                                                                                         |
|     └─TableFullScan_11      | 10000.00 | cop[tikv] | table:t1      | keep order:false, stats:pseudo                                                                                |
+-----------------------------+----------+-----------+---------------+---------------------------------------------------------------------------------------------------------------+
6 rows in set, 1 warning (0.00 sec)

What is changed and how it works?

This request fixs this case.

Check List

Tests

• Unit test

Release note

Fix the bug that sql got cancel if including json column joins char column.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• XuHuaiyu
• Yisaer

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-srebot]

/run-all-tests

[ti-srebot]

@Yisaer you're already a collaborator in bot's repo.

[XuHuaiyu]

LGTM

[zhouqiang-cl]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 0387a92

[ti-chi-bot]

@ti-srebot: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.