-
Notifications
You must be signed in to change notification settings - Fork 198
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
Replicas limit #465
Replicas limit #465
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.
added comment
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.
looks good! I just mentioned 1 more possible test you could add, but it shouldn't be a big deal
@@ -128,7 +128,7 @@ | |||
NsFields.hnsw_ef_construction: { | |||
"type": "integer", | |||
"minimum": 1, | |||
"maximum": int(read_env_vars_and_defaults(EnvVars.MARQO_EF_CONSTRUCTION_MAX_VALUE)), | |||
"maximum": read_env_vars_and_defaults_ints(EnvVars.MARQO_EF_CONSTRUCTION_MAX_VALUE), |
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.
may be the wrong PR to comment this on, but maybe we should rename MARQO_EF_CONSTRUCTION_MAX_VALUE
to MARQO_MAX_EF_CONSTRUCTION_VALUE
, because if you observe the other env vars, the word MAX
always comes first. It may confuse users if we keep EF like that.
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.
good thinking, to keep things consistent, but that would technically be a breaking change
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.
looks good! I just mentioned 1 more possible test you could add, but it shouldn't be a big deal
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
we add a new environmental variable, "MARQO_MAX_NUMBER_OF_REPLICAS" to control the maximum number of replicas that can be set when creating an index.
What is the current behavior? (You can also link to an open issue here)
no limit for number of replicas
What is the new behavior (if this is a feature change)?
we have this limit now
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
no
Have unit tests been run against this PR? (Has there also been any additional testing?)
running
Related Python client changes (link commit/PR here)
no
Related documentation changes (link commit/PR here)
will do
Other information:
no
Please check if the PR fulfills these requirements