You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.
Does it make sense to set the checkkey property to the default partitioning function to true?
Currently it's undefined which results in balancing to a certain partition even if we don't have a key specified. This in turn leads to partial results in certain search queries.
Do you see any obstacles in changing the default behaviour?
The text was updated successfully, but these errors were encountered:
As far as I can see in the dataflow we're not using the default and I don't think we need to change that, except we find really strong arguments to do so.
To me it looks like just changing the default, but ...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Does it make sense to set the
checkkey
property to the default partitioning function totrue
?Currently it's
undefined
which results in balancing to a certain partition even if we don't have a key specified. This in turn leads to partial results in certain search queries.Do you see any obstacles in changing the default behaviour?
The text was updated successfully, but these errors were encountered: