-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
executor, variable: move hidden variables to struct #24304
Conversation
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.
Nice!
@xhebox: In response to this: 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 ti-community-infra/tichi repository. |
@xhebox: In response to this:
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 ti-community-infra/tichi repository. |
@xhebox I've added sig-sql-infra if you want to try approving again. |
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.
OK. IIRC, the filter is introduced by our SIG anyway...
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 939a89f
|
What problem does this PR solve?
Problem Summary:
This moves the hidden attribute of a feature switch to the sysvar struct. This makes it possible for plugins to also create hidden variables, which may be a nice property in the future.
I also think it is useful for noop sysvars; since for many of them if they are hidden they will pass compatibility requirements, but not confuse users. I saw a user on TiDB slack today asking about setting
innodb_log_file_size
, which is a problem of our creation.What is changed and how it works?
What's Changed:
Internal refactor, function neutral.
Related changes
Check List
Tests
Side effects
Release note