-
Notifications
You must be signed in to change notification settings - Fork 61
Support Elasticsearch v8 #2783
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
Comments
p-kimberley
added a commit
to p-kimberley/stroom
that referenced
this issue
Feb 21, 2022
p-kimberley
added a commit
to p-kimberley/stroom
that referenced
this issue
Feb 22, 2022
The Elasticsearch Java High-Level REST Client has been deprecated and is in v7 maintenance mode. Until the newer Elasticsearch Java API Client matures, including supporting features like BulkProcessor, the existing v7.x client will be used with compatibility mode enabled, to support Elasticsearch v8 clusters. |
p-kimberley
added a commit
to p-kimberley/stroom
that referenced
this issue
Apr 27, 2022
" This reverts commit 2428892.
p-kimberley
added a commit
to p-kimberley/stroom
that referenced
this issue
Apr 29, 2022
Superseded by #2861 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Elasticsearch v8 included several changes to the REST API, in particular the removal of mapping types. See: https://www.elastic.co/guide/en/elastic-stack/current/elasticsearch-breaking-changes.html#_rest_api_changes.
This change causes errors when attempting to index documents using the current Stroom build against an Elasticsearch v8 cluster, as tracked in this issue.
To resolve this, the Stroom Elasticsearch REST client should be upgraded to >= v8.0.0.
The text was updated successfully, but these errors were encountered: