-
Notifications
You must be signed in to change notification settings - Fork 49
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
#348: Dependencies: Upgrade Elasticsearch to 8.0.0 #347
Conversation
Holding off on this until #360. I'm hoping that will let us maintain 7.x and 8.x concurrently. |
Hello, would it be possible to create an official pre-release of this ? Would like to test it on 8.3.2 |
You could try this:
|
@alexklibisz I see this issue is on hold while waiting for the |
@fabriziofortino No official timeline. I'm on vacation til Sept 20, so definitely not before then. Tentative plan is "sometime this fall". I'd happily review a PR if someone else wants to try it! Or, if you really want to get on v8, you can build off of this branch as described above. |
@fabriziofortino @nfsantos I got the merge conflicts resolved here.
Would be great if you guys could validate this works for you from the snapshot release. In particular the bit about the |
@alexklibisz We have validated the branch with the plugin for 8.4.1, but we cannot validate this one for 8.0. Elasticsearch 8.0 is not working for us because of a problem unrelated to this plugin. So we have to advance to 8.4.1. |
Related Issue
Link the related issues as a markdown list.
Changes
index.elastiknn
setting a no-op and stop using a custom codec. As of 9.0.0, Lucene issue 9843 is resolved, which means the default doc values codec is optimized for best speed. This means Elastiknn can stop overriding the codec. We keep the old custom codecs around for backwards-compatibility. This also resolves Deprecate index.elastiknn setting #254.Testing and Validation