-
Notifications
You must be signed in to change notification settings - Fork 1.3k
ReactiveElasticsearchClient should use the same request parameters as non-reactive code #1658
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
Hy @sothawo i would like to propose a PR for this issue. I have question about naming, in |
skip the new one. Once the existing and then deprecated method is removed we can reintroduce the Consumer based method with the new parameter. |
Is there any workaround for this other than using the non-reactive client for index-related operations? (Using the old |
Adapting this changes the API of Don't forget that Spring Data Elasticsearch is a community maintained project, there is no one working full time on this - and probably not in her payed working time. |
Currently the
ReactiveElasticsearchClient
uses old request classes for these operations:We should add variants that accept the same request classes as Elasticsearch's RestHighlevelClient and deprecate the existing ones for later removal.
The text was updated successfully, but these errors were encountered: