external: range job keys and region split keys are 2 concepts (part 1)

[lance6716]

What problem does this PR solve?

Issue Number: ref #55374

Problem Summary:

What changed and how does it work?

This is the first part of making job range keys and region split keys 2 different concetps, and it's only related to external engine changing. In next PR I'll change how lighting local backend will use them.

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

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

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.

[codecov]

Codecov Report

Attention: Patch coverage is 95.83333% with 4 lines in your changes missing coverage. Please review.

Project coverage is 57.0108%. Comparing base (f88409a) to head (40da059).
Report is 1 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #55659         +/-   ##
=================================================
- Coverage   72.8295%   57.0108%   -15.8188%     
=================================================
  Files          1583       1735        +152     
  Lines        443003     623203     +180200     
=================================================
+ Hits         322637     355293      +32656     
- Misses       100561     243260     +142699     
- Partials      19805      24650       +4845     

Flag	Coverage Δ
integration	39.4772% <71.8750%> (?)
unit	71.9592% <61.4583%> (-0.0016%)	⬇️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	62.3402% <ø> (+16.8854%)	⬆️

[lance6716]

/retest

[tiprow]

@lance6716: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[GMHDBJD]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-08-30 00:48:00.938490367 +0000 UTC m=+1090476.072940488: ☑️ agreed by D3Hunter.
• 2024-08-30 04:03:48.188229425 +0000 UTC m=+1102223.322679546: ☑️ agreed by GMHDBJD.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, GMHDBJD, ywqzzy

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:

• pkg/ddl/OWNERS [ywqzzy]
• pkg/disttask/OWNERS [D3Hunter,GMHDBJD,ywqzzy]
• pkg/lightning/OWNERS [D3Hunter,GMHDBJD]

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

[lance6716]

/retest

[tiprow]

@lance6716: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[lance6716]

/retest

[tiprow]

@lance6716: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.3: #55781.