executor: fix a bug that global temporary table send cop request

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #58875

Problem Summary:

What changed and how does it work?

For temporary table, we set a 'dummy' flag to its TableReader/IndexReader/IndexReader etc
So it would be a dummy operation and not sending coprocessor request to tikv.

The bug is that in executor/builder.go, we have executorBuilder and dataReaderBuilder, two difficult code branch.
The dummy is only set in the executorBuilder...

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 @tiancaiamao. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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-sigs/prow repository.

[tiancaiamao]

/check-issue-triage-complete

[hawkingrei]

/ok-to-test

[windtalker]

lgtm

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.5277%. Comparing base (7ca323f) to head (1c98fa6).
Report is 61 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58882        +/-   ##
================================================
+ Coverage   73.1228%   73.5277%   +0.4048%     
================================================
  Files          1678       1678                
  Lines        464071     464935       +864     
================================================
+ Hits         339342     341856      +2514     
+ Misses       103871     102237      -1634     
+ Partials      20858      20842        -16     

Flag	Coverage Δ
integration	42.9501% <100.0000%> (?)
unit	72.3348% <100.0000%> (+0.0287%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	45.6909% <ø> (-0.0092%)	⬇️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lcwangchao, windtalker

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 [lcwangchao,windtalker]

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:

• 2025-01-13 08:24:12.535228237 +0000 UTC m=+773995.824059942: ☑️ agreed by windtalker.
• 2025-01-13 09:03:02.087658745 +0000 UTC m=+776325.376490453: ☑️ agreed by lcwangchao.

[hawkingrei]

/retest

[tiancaiamao]

/test check-dev2

[tiprow]

@tiancaiamao: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test check-dev2

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-sigs/prow repository.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #58979.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #59059.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #59114.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #59115.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #59116.