-
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
Variables should use status var interface #9381
Comments
PTAL @tiancaiamao Do you see any flaws in this strategy? |
individual components 'register' sysvars sounds a good idea. |
+1 plugin also needs a mechanism to "register sysvar" into hosted TiDB too, and now plugins use ugly way to do it. we should improve it. |
@lysu do you mind if I take this over? |
I meant I would like to work on this if that is okay with you :) I think it works best as multiple PRs:
|
👍 Yes, it's ok for me~ 😊 |
Feature Request
Is your feature request related to a problem? Please describe:
I found a bug in #9365
It looks like the variables are initialized before the config file is parsed. So if the port is non-default, it won't be reflected.
Describe the feature you'd like:
Instead of having configuration all in one place, I think a nicer design would be to have individual components 'register' sysvars. This would make it work closer to how status vars currently work.
The advantage would be that plugins could also add additional variables to the server.
(This would make it work similar to MySQL too..)
Describe alternatives you've considered:
An easy workaround would be to update the sysvars after the server starts.
Teachability, Documentation, Adoption, Migration Strategy:
It would take some initial work to move sysvars to the correct component. Initially, they could all be put under the server.
The text was updated successfully, but these errors were encountered: