executor: fix plan replay cannot deal with placement mode

[hawkingrei]

What problem does this PR solve?

Issue Number: close #54961

Problem Summary:

What changed and how does it work?

when we restore the table with plan replay. we will ignore the placement rules to success to create table.

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-10-22 09:12:35.525353226 +0000 UTC m=+342356.222143836: ☑️ agreed by winoros.
• 2024-10-22 09:16:03.480794767 +0000 UTC m=+342564.177585369: ☑️ agreed by XuHuaiyu.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.2517%. Comparing base (44f1c14) to head (e926caa).
Report is 14 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #56774         +/-   ##
=================================================
- Coverage   73.3610%   56.2517%   -17.1094%     
=================================================
  Files          1634       1759        +125     
  Lines        452548     631449     +178901     
=================================================
+ Hits         331994     355201      +23207     
- Misses       100190     252261     +152071     
- Partials      20364      23987       +3623     

Flag	Coverage Δ
integration	36.4935% <0.0000%> (?)
unit	72.4894% <100.0000%> (-0.0057%)	⬇️

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

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	52.6695% <ø> (+6.6496%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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,XuHuaiyu,winoros]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hawkingrei]

/cherrypick release-8.4

[hawkingrei]

/cherrypick release-8.1
/cherrypick release-7.5

[ti-chi-bot]

@hawkingrei: new pull request created to branch release-8.4: #56778.

In response to this:

/cherrypick release-8.4

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]

@hawkingrei: new pull request created to branch release-7.5: #56779.

In response to this:

/cherrypick release-8.1
/cherrypick release-7.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]

@hawkingrei: new pull request created to branch release-8.1: #56780.

In response to this:

/cherrypick release-8.1
/cherrypick release-7.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-7.1: #56824.