cdf67e0fd5
This PR adds support for using the `slice` option in point-in-time searches. By default, the slice query splits documents based on their Lucene ID. This strategy is more efficient than the one used for scrolls, which is based on the `_id` field and must iterate through the whole terms dictionary. When slicing a search, the same point-in-time ID must be used across slices to guarantee the partitions don't overlap or miss documents. Closes #65740. |
||
|---|---|---|
| .. | ||
| search-your-data | ||
| suggesters | ||
| async-search.asciidoc | ||
| clear-scroll-api.asciidoc | ||
| count.asciidoc | ||
| explain.asciidoc | ||
| field-caps.asciidoc | ||
| multi-search-template-api.asciidoc | ||
| multi-search.asciidoc | ||
| point-in-time-api.asciidoc | ||
| profile.asciidoc | ||
| rank-eval.asciidoc | ||
| render-search-template-api.asciidoc | ||
| scroll-api.asciidoc | ||
| search-shards.asciidoc | ||
| search-template-api.asciidoc | ||
| search.asciidoc | ||
| suggesters.asciidoc | ||
| terms-enum.asciidoc | ||
| validate.asciidoc | ||