-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[chore](config) support select experimental session variable #31837
Conversation
run buildall |
run buildall |
run buildall |
1 similar comment
run buildall |
run buildall |
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
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
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
support select experimental variables: Before change: Before change: select @@experimental_enable_nereids_planner; ERROR 1193 (HY000): errCode = 2, detailMessage = Unknown system variable 'experimental_enable_nereids_planner' show variables like 'experimental_enable_nereids_planner'; +-------------------------------------+-------+---------------+---------+ | Variable_name | Value | Default_Value | Changed | +-------------------------------------+-------+---------------+---------+ | experimental_enable_nereids_planner | false | true | 1 | +-------------------------------------+-------+---------------+---------+ After change: > select @@experimental_enable_nereids_planner; +---------------------------------------+ | @@experimental_enable_nereids_planner | +---------------------------------------+ | 1 | +---------------------------------------+
Proposed changes
support select experimental variables:
Before change:
After change:
Further comments
If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...