Peter-Josef Meisch
Peter-Josef Meisch
Spring Data Elasticsearch should support the [point in time (PIT) API](https://www.elastic.co/guide/en/elasticsearch/reference/7.10/point-in-time-api.html). This is needed together with search_after (#1143) to redesign paging through large result sets, which currently is done with...
These two methods are used inconsistently, it seems that not all requests do a proper conversion of an `ID` but only a string representation - for example when indexing an...
This is to keep track of https://github.com/elastic/elasticsearch-java/issues/298 in this project
This issue is for keeping track of https://github.com/elastic/elasticsearch-java/issues/286 in this project.
This issue is for keeping track of https://github.com/elastic/elasticsearch-java/issues/264 in this project. Putting this in a separate issue to be able to proceed with https://github.com/spring-projects/spring-data-elasticsearch/issues/1973.
Currently there is no possibility to set the size of the single requests that are sent to the cluster when scrolling through all records (see #2023), the current code always...
Spring Data Elasticsearch should add support for the Task API (https://www.elastic.co/guide/en/elasticsearch/reference/current/tasks.html): * add methods to the `ClusterOperations` according to the ES API * add methods like `submitDelete(Query) (https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-delete-by-query.html#docs-delete-by-query-task-api) that create...
Follow-up to #1725, there was a `SearchTemplateRequestBuilder` added to the `NativeSearchQuery`, but that is not the right place. We need to define the parameters for a search template request and...
Currently streaming result data is based on the scroll API. This is not recommanded by Elasticsearch anymore, instead one should use search_after (~#1143~) and point in time (#1684).
Since Elasticsearch 8.4 there is a bug in Elasticsearch (see https://github.com/elastic/elasticsearch/issues/89760) which can lead to Elasticsearch not returning the correct number of hits. This will then result incorrect results returned...