-
Notifications
You must be signed in to change notification settings - Fork 3.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
sql: remove 'experimental_always' as an option for vectorize cluster setting #39285
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.
What about just removing the "experimental_always" setting from the cluster setting?
092a314
to
c16b7e3
Compare
I didn't even realize it was an option! Thanks, it's a lot cleaner this way. Also, is there a way to "advertise" |
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 - I'm not sure if there's a particular way to "advertise" the setting besides normal documentation.
…setting If we allow such thing, then it is quite painful to reset the cluster setting. It is also quite tricky to allow the corresponding query to go around the vectorized engine when the vectorize cluster setting is 'experimental_vectorize` even if the session variable is 'off' because the internal executor uses the cluster setting. Release note: None
c16b7e3
to
0ea31a8
Compare
I guess if someone really wants to use TFTR! bors r+ |
39285: sql: remove 'experimental_always' as an option for vectorize cluster setting r=yuzefovich a=yuzefovich If we allow such thing, then it is quite painful to reset the cluster setting. It is also quite tricky to allow the corresponding query to go around the vectorized engine when the vectorize cluster setting is 'experimental_vectorize` even if the session variable is 'off' because the internal executor uses the cluster setting. Release note: None Co-authored-by: Yahor Yuzefovich <yahor@cockroachlabs.com>
Build succeeded |
If we allow such thing, then it is quite painful to reset the
cluster setting. It is also quite tricky to allow the corresponding
query to go around the vectorized engine when the vectorize cluster
setting is 'experimental_vectorize` even if the session variable is
'off' because the internal executor uses the cluster setting.
Release note: None