Skip to content
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

Upgrade to Elasticsearch 7.17.1 #2108

Closed
sothawo opened this issue Mar 6, 2022 · 2 comments · Fixed by #2109
Closed

Upgrade to Elasticsearch 7.17.1 #2108

sothawo opened this issue Mar 6, 2022 · 2 comments · Fixed by #2109
Assignees
Labels
type: task A general task

Comments

@sothawo
Copy link
Collaborator

sothawo commented Mar 6, 2022

No description provided.

@sothawo sothawo added the type: task A general task label Mar 6, 2022
@sothawo sothawo self-assigned this Mar 6, 2022
@sothawo sothawo added this to To do in what's up next? Mar 6, 2022
@sothawo sothawo moved this from To do to In progress in what's up next? Mar 6, 2022
sothawo added a commit to sothawo/spring-data-elasticsearch that referenced this issue Mar 6, 2022
what's up next? automation moved this from In progress to Done Mar 6, 2022
sothawo added a commit that referenced this issue Mar 6, 2022
@linghengqian
Copy link

Will there be any timeline to move the default ElasticSearch version to 8.0.1 or 8.1.0?( I refer, of course, to the attributes in pom.xml )

@sothawo
Copy link
Collaborator Author

sothawo commented Mar 15, 2022

@linghengqian With Spring Data Elasticsearch version 5. Using Elasticsearch 8 means we have to use the new client because the RestHighlevelClient is not available anymore in 8. But that forces the application to use the jakarta. packages instead of javax. packages because the new client needs that. Spring will change to that with the next version 6, and for Spring Data Elasticsearch that means version 5 then.

Besides that I am still working on integrating the new client from version 7.17.x into Spring Data Elasticsearch as an alternative for Spring Data Elasticsearch 4.4, but there is still work to be done - and there are still bugs in that client.

If you have an Elasticsearch 8 cluster you can set the compatibility headers, but I found and raised an issue for that that form some answer the Elasticsearch 8 cluster returns non compatible answers despite the headers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants