planner: remove old useless unfinished index advisor implementation

[qw4990]

What problem does this PR solve?

Issue Number: ref #12303

Problem Summary: planner: remove old useless unfinished index advisor implementation

What changed and how does it work?

planner: remove old useless unfinished index advisor implementation

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-09-03 06:39:46.645326111 +0000 UTC m=+340111.163379034: ☑️ agreed by hawkingrei.
• 2024-09-03 06:42:39.432670566 +0000 UTC m=+340283.950723495: ☑️ agreed by AilinKid.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.4460%. Comparing base (939c97f) to head (c9359e2).
Report is 6 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #55810         +/-   ##
=================================================
- Coverage   72.7926%   56.4460%   -16.3466%     
=================================================
  Files          1588       1713        +125     
  Lines        443469     617072     +173603     
=================================================
+ Hits         322813     348313      +25500     
- Misses       100782     245369     +144587     
- Partials      19874      23390       +3516     

Flag	Coverage Δ
integration	37.6086% <ø> (?)
unit	72.2072% <ø> (+0.3038%)	⬆️

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

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

[elsa0520]

LGTM

[qw4990]

/test check_dev

[ti-chi-bot]

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

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pull-br-integration-test
• /test pull-integration-ddl-test
• /test pull-lightning-integration-test
• /test pull-mysql-client-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test canary-notify-when-compatibility-sections-changed
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-common-test
• /test pull-e2e-test
• /test pull-integration-common-test
• /test pull-integration-copr-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test pull-integration-nodejs-test
• /test pull-sqllogic-test
• /test pull-tiflash-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test
• pingcap/tidb/pull_integration_ddl_test
• pingcap/tidb/pull_mysql_client_test

In response to this:

/test check_dev

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/test-infra repository.

[tiprow]

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

In response to this:

/test check_dev

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.

[qw4990]

/ok-to-test

[qw4990]

/test check-dev2

[tiprow]

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

[yudongusa]

LGTM. Please also modify the corresponding documents.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, elsa0520, hawkingrei, tangenta, yudongusa

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,elsa0520,hawkingrei,tangenta]
• pkg/parser/OWNERS [tangenta,yudongusa]
• pkg/planner/OWNERS [AilinKid,elsa0520,hawkingrei]

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

[qw4990]

/test unit-test

[tiprow]

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