import-into: support running with 1 thread when using global sort

[joccau]

What problem does this PR solve?

Issue Number: close #58680

Problem Summary:

What changed and how does it work?

• The feature of import into can be run with the option of thread=1
• Simplify the code.

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.

The feature of `import into` with the options `global-sort` can be run at the server that only consumes 1 core resource.

[codecov]

Codecov Report

Attention: Patch coverage is 80.64516% with 6 lines in your changes missing coverage. Please review.

Project coverage is 73.3884%. Comparing base (d93c233) to head (516d575).
Report is 1 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58572        +/-   ##
================================================
+ Coverage   72.9581%   73.3884%   +0.4302%     
================================================
  Files          1697       1697                
  Lines        468911     468932        +21     
================================================
+ Hits         342109     344142      +2033     
+ Misses       105737     103739      -1998     
+ Partials      21065      21051        -14     

Flag	Coverage Δ
integration	42.7869% <0.0000%> (?)
unit	72.1713% <80.6451%> (+0.0225%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	45.1107% <ø> (+0.0112%)	⬆️

[joccau]

/test pull-lightning-integration-test

[tiprow]

@joccau: 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 pull-lightning-integration-test

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.

[joccau]

/test unit-test

[tiprow]

@joccau: 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 unit-test

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.

[joccau]

/test pull-lightning-integration-test

[lance6716]

only consume 1 core resource.

If the goal is during the whole IMPORT INTO only ~100% CPU is used, I think your internal test report can't achieve it.

[D3Hunter]

/hold

this PR and related test hasn't reproduced the OOM we meet before, so there is no optimization for memory

[joccau]

/unhold

[D3Hunter]

rest lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, lance6716

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 [D3Hunter,lance6716]
• pkg/disttask/OWNERS [D3Hunter,lance6716]
• pkg/executor/importer/OWNERS [D3Hunter,lance6716]
• pkg/meta/OWNERS [D3Hunter,lance6716]

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-02-21 08:19:59.696832802 +0000 UTC m=+1208642.093054859: ☑️ agreed by D3Hunter.
• 2025-02-24 03:25:44.421860066 +0000 UTC m=+239892.375018330: ☑️ agreed by lance6716.

[joccau]

/test check-dev2

[tiprow]

@joccau: 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.