18866c4c0b
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 |
||
|---|---|---|
| .. | ||
| src/main/java/org/elasticsearch/plugin/noop | ||
| README.md | ||
| build.gradle | ||
README.md
Purpose
This plugin provides empty REST and transport endpoints for bulk indexing and search. It is used to avoid accidental server-side bottlenecks in client-side benchmarking.
Build Instructions
Build the plugin with gradle :client:client-benchmark-noop-api-plugin:assemble from the Elasticsearch root project directory.
Installation Instructions
After, the binary has been built, install it with bin/elasticsearch-plugin install file:///full/path/to/noop-plugin.zip.
Usage
The plugin provides two REST endpoints:
/_noop_bulkand all variations that the bulk endpoint provides (except that all no op endpoints are called_noop_bulkinstead of_bulk)_noop_searchand all variations that the search endpoint provides (except that all no op endpoints are called_noop_searchinstead of_search)
The corresponding transport actions are:
org.elasticsearch.plugin.noop.action.bulk.TransportNoopBulkActionorg.elasticsearch.plugin.noop.action.search.TransportNoopSearchAction