-
Notifications
You must be signed in to change notification settings - Fork 99
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
Elasticsearch 7 will become EOL #9405
Comments
Elastic search EOL estimate
Elasticsearch all version support table
source: elastic search |
So according to above table we should migrate directly to 9? Else we would be doing it again in 6 months, worst case scenario. |
@jelmerveen 7 will be supported for 6 months after elasticsearch 9 is released. After that 8 will be supported much longer. Migrating directly to 9 will probably require lots of code changes because the old java client is deprecated. |
But as I read it, 8 will not even make it until 2024 perhaps. As you can read in the top table:
|
Ah yes you are right! Depending on when 9 is released it is possible that migrating to 9 at once is much more efficiënt. This will require a much more drastic refactoring because I don't think the current java API is still supported. |
Elasticsearch 17.7 (the version we are/should be using) is supported until 6 months after Elasticsearch 9.0 comes out.
After that we need to migrate to ES8. The ES Java REST client we use is deprecated, however it can be run in compatibility mode so we don't need to upgrade to the new Java API client yet. This requires a small code change, see this manual page. The
RestHighLevelClient
is created inorg.molgenis.data.elasticsearch.client.ClientFactory
and can be changed there to enable the compatibility mode.Then follow the migragion guide
The text was updated successfully, but these errors were encountered: