-
Notifications
You must be signed in to change notification settings - Fork 753
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
feat(setting): support global setting #6579
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Do we need to prevent users to set a 4mb value which could break our meta services? |
Users can not set a global setting which not in our settings, so this example:
is not right, we can only set the settings(show settings) not user-defined as |
Yes, the summary is inaccurate. |
Not sure the CI failure is related to this PR, please have a check @fkuner |
I think failed test is not related to this pr. |
@mergify update |
✅ Branch has been successfully updated |
The sqllogic test has many errors. I am uncertian whether it's related to thir pr. Please have a look. @ZeaLoVe |
Hi, can you update the summary so newcomers will not be confused?
I have merged against the main branch. Let's have a look. |
Have updated the summary. |
|
Yes, it seems not to be related to this pr. |
logictest failed fix in #6593 |
I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/
Summary
set global max_threads = 16;
The setting
max_thread
must be in our settings which will be displayed whenshow settings;
The global setting will be stored in metasrv according to
tenant
. So each tenant has their own global setting and can be shared on different sessions. Clients can also executeset max_threads = 8
to override global setting in session granularity.Fixes #3933