*: AnalyzeV2 supports processing special global indexes

[Defined2014]

What problem does this PR solve?

Issue Number: close #54233

Problem Summary:

Supports processing global index in analyze version V2. Because the data of the global index is not scattered in every partitions, only one analyze is required for the whole table.

Because we use an independent index analyze task, there will be results of the same version when saving, which needs to be processed like mv index.

After the analysis is complete, the global index will only have global stats.

AutoAnalyze will not process global index, user should trigger it manually.

What changed and how does it work?

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 @Defined2014. 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.

[Defined2014]

/retest

[tiprow]

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

[hawkingrei]

/ok-to-test

[codecov]

Codecov Report

Attention: Patch coverage is 93.05556% with 10 lines in your changes missing coverage. Please review.

Project coverage is 76.2802%. Comparing base (2ef0a36) to head (24a40d3).
Report is 178 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #56115        +/-   ##
================================================
+ Coverage   73.4587%   76.2802%   +2.8215%     
================================================
  Files          1605       1627        +22     
  Lines        444802     453922      +9120     
================================================
+ Hits         326746     346253     +19507     
+ Misses        98001      86332     -11669     
- Partials      20055      21337      +1282     

Flag	Coverage Δ
integration	52.2146% <88.8888%> (?)
unit	72.7585% <77.7777%> (+0.2147%)	⬆️

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

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

[Rustin170506]

Thanks!

[Rustin170506]

rest LGTM

/hold

Feel free to unhold it after you fix them. Or feel free to cc me to look at it again.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-09-24 09:37:04.507734667 +0000 UTC m=+1558694.248158599: ☑️ agreed by Rustin170506.
• 2024-09-24 15:37:04.18100501 +0000 UTC m=+1580293.921428951: ☑️ agreed by winoros.

[winoros]

But don't forget to add the comments requested by Rustin.

[tiprow]

@Defined2014: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	24a40d3	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[Defined2014]

/unhold

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Rustin170506, tangenta, winoros

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 [Rustin170506,tangenta,winoros]
• pkg/ddl/OWNERS [tangenta]
• pkg/planner/OWNERS [Rustin170506,winoros]
• pkg/statistics/OWNERS [Rustin170506,winoros]

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