-
Notifications
You must be signed in to change notification settings - Fork 126
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
Add rolling version upgrade support for ignore_unmapped #1770
base: main
Are you sure you want to change the base?
Add rolling version upgrade support for ignore_unmapped #1770
Conversation
@kotwanikunal thanks for raising the PR. Will wait for all BWC to gh actions to complete. |
@kotwanikunal can you fix the failed GH actions? |
Good finding, we should do same in other repos. Will approve once CI is fixed. Current error is from spotless, you can run |
Pushed linting fixes in. |
Looks related to the change. Let me take a look
|
@@ -324,7 +326,7 @@ protected void doWriteTo(StreamOutput out) throws IOException { | |||
out.writeFloatArray(vector); | |||
out.writeInt(k); | |||
out.writeOptionalNamedWriteable(filter); | |||
if (isClusterOnOrAfterMinRequiredVersion("ignore_unmapped")) { | |||
if (out.getVersion().onOrAfter(getMinVersionForFeature("ignore_unmapped"))) { |
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.
Does this stream guarantee the min version of the cluster. Just verifying since the previous method has that check
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.
Is there a historical reason that we look for the cluster version and not the stream version?
It should behave the same - a feature is on only when both the nodes are upgraded.
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 haven't serialized the stream version when we write KNNQueryBuilder at first. Therefore, we were not able to use stream version. After that, we haven't tried to add stream version because cluster version just worked fine for us.
@kotwanikunal is there pending? |
Signed-off-by: Kunal Kotwani <[email protected]>
Signed-off-by: Kunal Kotwani <[email protected]>
Signed-off-by: Kunal Kotwani <[email protected]>
7550f9e
to
3aa15a2
Compare
I had a rebase pending. |
Description
ignore_unmapped
Issues Resolved
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.