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
Elastic search provides an option to add a path param to any search queries called _request_cache=true which enables it to cache any incoming queries and its results.
The SearchRequest class provides a way to add this param using the .requestCache(Boolean.TRUE) method. But the RequestFactory.java present in Spring DATA that converts a NativeSearchQuery into SearchRequest doesn't support this argument.
Thus this parameter cannot be added to any request for search using ReactiveElasticSearchOperations
The reactive implementation of search request under the hood uses Elasticsearch's scroll API to retrieve the documents. request_cachecannot be used in a scroll context.
For the imperative, non-reactive code this is done in #1797
not all reactive calls use the scroll interface, paged queries and count do not. So this needs to be added to these calls. Doing imperative with this ticket as well.
sothawo
changed the title
ReactiveElasticsearchOperations does not have option to include request_cache path param in search request [DATAES-992]
(Reactive)ElasticsearchOperations does not have option to include request_cache path param in search request [DATAES-992]
May 1, 2021
Oindrila Barik opened DATAES-992 and commented
Elastic search provides an option to add a path param to any search queries called _request_cache=true which enables it to cache any incoming queries and its results.
The SearchRequest class provides a way to add this param using the .requestCache(Boolean.TRUE) method. But the RequestFactory.java present in Spring DATA that converts a NativeSearchQuery into SearchRequest doesn't support this argument.
Thus this parameter cannot be added to any request for search using ReactiveElasticSearchOperations
No further details from DATAES-992
The text was updated successfully, but these errors were encountered: