-
Notifications
You must be signed in to change notification settings - Fork 473
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
Support CLI options for kvrocks server #1037
Conversation
wow, so speedy. |
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.
We'd better guard config keys with a namespace.
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. Then I have no objection on the option format. More comments inline.
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.
I test with ./build/kvrocks --unknown k
and it starts well. I'm thinking of whether we should fail if the config key is unknown.
@@ -61,6 +61,14 @@ struct CompactionCheckerRange { | |||
bool Enabled() { return Start != -1 || Stop != -1; } | |||
}; | |||
|
|||
struct CLIOptions { |
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.
nit: I'd prefer as simple as Options
.
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.
I think Options
is not specific enough.
If you put an |
Thanks all. Merging... |
It closes #1034