-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*: collect index usage information from point get and dump them to KV #20126
Conversation
/label componet/statistics |
These labels are not found |
/label component/statistics |
/label sig/planner |
/cc @qw4990 |
Co-authored-by: Yuanjia Zhang <qw4990@163.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
```sql | ||
create table SCHEMA_INDEX_USAGE ( | ||
TABLE_SCHEMA varchar(64), | ||
TABLE_NAME varchar(64), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'd better store table id and index id?
The table name and index name can be changed by ddl stmt.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think name is more user-friendly than id. And there are two solutions to this problem.
- One is to handle the DDL of rename to modify the name in the table.
- And the other is to create a more user-friendly view based on this table.
I prefer the latter. If you agree, I'll modify it in next PR and write it in the document.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The second one LGTM.
/merge |
/run-all-tests |
@rebelice merge failed. |
/run-unit-test |
What problem does this PR solve?
Issue Number: #19209
Problem Summary:
Collect index usage information from point get and dump them to KV.
This is a part of #19209 . And I'll collect index usage information from others in the following pr.
What is changed and how it works?
Proposal: Index usage information
What's Changed:
How it Works:
Related changes
Check List
Side effects
Release note