*: add extractor for cluster_tidb_index_usage

[joechenrh]

What problem does this PR solve?

Issue Number: ref #50305

What changed and how does it work?

InfoSchemaIndexUsageExtractor is added for cluster_tidb_index usage memtable.

Besides, the explain output of cluster memory table is changed to make it consistent with other memtable.

mysql> explain select * from information_schema.CLUSTER_TIDB_INDEX_USAGE where table_schema = "test";    
+------------------------+----------+-----------+--------------------------------+----------------------------------------------------------------------+
| id                     | estRows  | task      | access object                  | operator info                                                        |
+------------------------+----------+-----------+--------------------------------+----------------------------------------------------------------------+
| TableReader_7          | 10.00    | root      |                                | data:Selection_6                                                     |
| └─Selection_6          | 10.00    | cop[tidb] |                                | eq(information_schema.cluster_tidb_index_usage.table_schema, "test") |
|   └─MemTableScan_5     | 10000.00 | cop[tidb] | table:CLUSTER_TIDB_INDEX_USAGE |                                                                      |
+------------------------+----------+-----------+--------------------------------+----------------------------------------------------------------------+

Before:

mysql> explain select * from information_schema.CLUSTER_TIDB_INDEX_USAGE where table_schema = "test";                                                                                 
+-------------------------+----------+-----------+--------------------------------+----------------------------------------------------------------------+                            
| id                      | estRows  | task      | access object                  | operator info                                                        |                            
+-------------------------+----------+-----------+--------------------------------+----------------------------------------------------------------------+                            
| TableReader_7           | 10.00    | root      |                                | data:Selection_6                                                     |                            
| └─Selection_6           | 10.00    | cop[tidb] |                                | eq(information_schema.cluster_tidb_index_usage.table_schema, "test") |                            
|   └─TableFullScan_5     | 10000.00 | cop[tidb] | table:CLUSTER_TIDB_INDEX_USAGE | keep order:false, stats:pseudo                                       |                            
+-------------------------+----------+-----------+--------------------------------+----------------------------------------------------------------------+                            

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

All modified and coverable lines are covered by tests ✅

Project coverage is 75.0836%. Comparing base (eeb3d73) to head (5ac9b29).
Report is 10 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55416        +/-   ##
================================================
+ Coverage   74.8640%   75.0836%   +0.2196%     
================================================
  Files          1576       1578         +2     
  Lines        365691     443829     +78138     
================================================
+ Hits         273771     333243     +59472     
- Misses        72108      90462     +18354     
- Partials      19812      20124       +312     

Flag	Coverage Δ
integration	49.4430% <66.6666%> (?)
unit	72.1762% <100.0000%> (-1.6542%)	⬇️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (-2.2327%)	⬇️
parser	∅ <ø> (∅)
br	52.5529% <ø> (+4.7549%)	⬆️

[joechenrh]

/ok-to-test

[tangenta]

Maybe add a method ListSchemasAndTables for InfoSchemaIndexUsageExtractor and avoid using SchemaTableInfos.

[joechenrh]

InfoSchemaIndexUsageExtractor has already implemented schema and table filter, which is used in tidb_index_usage.
The only difference is that for cluster_tidb_index_usage, the request needs to be sent to all tidb instances for execution

[joechenrh]

Oops, I forgot to push some code.

[tiancaiamao]

What's the difference between clustered_index_usage table and tidb_index_usage table?

[tiancaiamao]

OK, different tidb at the same time may see different schema.

[joechenrh]

https://docs.pingcap.com/tidb/stable/information-schema-tidb-index-usage#tidb_index_usage

I think each tidb will collect its own index-related statistics.

[joechenrh]

For example, I ran some query on one node and got this output.

mysql> select * from information_schema.CLUSTER_TIDB_INDEX_USAGE where table_schema = "test" and index_name = "idx_1";
+-----------------+--------------+------------+------------+-------------+--------------+-------------------+---------------------+-----------------------+------------------------+-------------------------+-------------------------+--------------------------+-----------------------+---------------------+
| INSTANCE        | TABLE_SCHEMA | TABLE_NAME | INDEX_NAME | QUERY_TOTAL | KV_REQ_TOTAL | ROWS_ACCESS_TOTAL | PERCENTAGE_ACCESS_0 | PERCENTAGE_ACCESS_0_1 | PERCENTAGE_ACCESS_1_10 | PERCENTAGE_ACCESS_10_20 | PERCENTAGE_ACCESS_20_50 | PERCENTAGE_ACCESS_50_100 | PERCENTAGE_ACCESS_100 | LAST_ACCESS_TIME    |
+-----------------+--------------+------------+------------+-------------+--------------+-------------------+---------------------+-----------------------+------------------------+-------------------------+-------------------------+--------------------------+-----------------------+---------------------+
| 127.0.0.1:10081 | test         | t          | idx_1      |           0 |            0 |                 0 |                   0 |                     0 |                      0 |                       0 |                       0 |                        0 |                     0 | NULL                |
| 127.0.0.1:10080 | test         | t          | idx_1      |           1 |            1 |                 3 |                   0 |                     0 |                      0 |                       0 |                       0 |                        1 |                     0 | 2024-08-15 09:46:04 |
+-----------------+--------------+------------+------------+-------------+--------------+-------------------+---------------------+-----------------------+------------------------+-------------------------+-------------------------+--------------------------+-----------------------+---------------------+

[joechenrh]

/assign hi-rustin

[ti-chi-bot]

@joechenrh: GitHub didn't allow me to assign the following users: hi-rustin.

Note that only pingcap members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign hi-rustin

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.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-08-15 00:23:52.339260163 +0000 UTC m=+400317.042729806: ☑️ agreed by tiancaiamao.
• 2024-08-15 05:54:06.132455204 +0000 UTC m=+420130.835924865: ☑️ agreed by tangenta.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: GMHDBJD, hawkingrei, tangenta, tiancaiamao

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 [GMHDBJD,hawkingrei,tangenta,tiancaiamao]
• pkg/infoschema/OWNERS [GMHDBJD,tangenta]
• pkg/planner/OWNERS [hawkingrei]

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

[joechenrh]

/test check-dev2

[tiprow]

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