You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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.
No description provided.
The text was updated successfully, but these errors were encountered: