OpenSearch/client
Jim Ferenczi 18866c4c0b
Make hits.total an object in the search response (#35849)
This commit changes the format of the `hits.total` in the search response to be an object with
a `value` and a `relation`. The `value` indicates the number of hits that match the query and the
`relation` indicates whether the number is accurate (in which case the relation is equals to `eq`)
or a lower bound of the total (in which case it is equals to `gte`).
This change also adds a parameter called `rest_total_hits_as_int` that can be used in the
search APIs to opt out from this change (retrieve the total hits as a number in the rest response).
Note that currently all search responses are accurate (`track_total_hits: true`) or they don't contain
`hits.total` (`track_total_hits: true`). We'll add a way to get a lower bound of the total hits in a
follow up (to allow numbers to be passed to `track_total_hits`).

Relates #33028
2018-12-05 19:49:06 +01:00
..
benchmark Use Gradle wrapper in client benchmark README 2018-11-08 15:32:47 +01:00
client-benchmark-noop-api-plugin Make hits.total an object in the search response (#35849) 2018-12-05 19:49:06 +01:00
rest LLREST: Add PreferHasAttributeNodeSelector (#36005) 2018-11-28 16:29:05 -05:00
rest-high-level Make hits.total an object in the search response (#35849) 2018-12-05 19:49:06 +01:00
sniffer Checkstyle: Catch wide snippets (#34163) 2018-10-01 15:22:15 -04:00
test Run forbidden api checks with runtimeJavaVersion (#32947) 2018-08-22 09:05:22 +03:00
transport Run forbidden api checks with runtimeJavaVersion (#32947) 2018-08-22 09:05:22 +03:00