planner: fix range partition prune bug for IN expr (#22894) (#22938)

[ti-srebot]

cherry-pick #22938 to release-4.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/23074

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

git push git@github.com:ti-srebot/tidb.git pr/23074:release-4.0-3f7a573caacb

---

Signed-off-by: guo-shaoge shaoge1994@163.com

What problem does this PR solve?

Issue Number: close #22894

Problem Summary: The implementation of partition prune for IN expression got bug. We should use part_fn(const_arg_of_IN_expr) to calc partition id, but the current implement just use const_arg_of_IN_expr to calc partition id.

What is changed and how it works?

What's Changed: change planner.core.partitionRangeForInExpr()

How it Works: Change partitionRangeForInExpr(). For each const arg of IN expr, if part_fn is not nil, use part_fn(const_arg_of_IN_expr) to calc partition id. Otherwise, use const_arg_of_IN_expr to calc partition id.

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Integration test

• Manual test (add detailed scripts or steps below)

  use test;
  drop table if exists IDT_RP2205;
  CREATE TABLE `IDT_RP2205` (   `COL1` tinyint(11) DEFAULT '24' COMMENT 'NUMERIC UNIQUE INDEX') 
  PARTITION BY RANGE ( `COL1`%2 ) (
      PARTITION `P0` VALUES LESS THAN (0),
      PARTITION `P1` VALUES LESS THAN (10),
      PARTITION `P2` VALUES LESS THAN (20),
      PARTITION `P3` VALUES LESS THAN (30),
      PARTITION `P4` VALUES LESS THAN (40),
      PARTITION `P5` VALUES LESS THAN (50),
      PARTITION `PMX` VALUES LESS THAN (MAXVALUE) );
  insert into IDT_RP2205 values(127);
  select * from IDT_RP2205 where col1 in (127);
  select * from IDT_RP2205 where col1 in (127,127);
  

Side effects: No side effects

Release note

• fix range partition prune bug for IN expr

[ti-srebot]

/run-all-tests

[ti-srebot]

@guo-shaoge you're already a collaborator in bot's repo.

[guo-shaoge]

/retest

[guo-shaoge]

/run-all-tests

[zhouqiang-cl]

/run-check-release-note

[tiancaiamao]

/LGTM

[tiancaiamao]

PTAL @crazycs520

[tiancaiamao]

PTAL @crazycs520

[crazycs520]

LGTM

[ti-chi-bot]

@crazycs520: Please use /LGTM instead of LGTM when you want to approve the pull request by comment.
If you use the GitHub review feature, please approve the PR directly, the comment will not take effect in the GitHub review feature.
If you have any qustions please refer to lgtm command help or lgtm plugin design.

If you have approved this PR, please ignore this reply. This reply is being used as a temporary reply during the migration of the new bot and will be removed on April 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.

[crazycs520]

/lgtm
/approve

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• crazycs520
• tiancaiamao

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[tiancaiamao]

/merge

[ti-chi-bot]

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

Commit hash: f966699

[zhouqiang-cl]

/merge

[zhouqiang-cl]

/merge

[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.