From d59ec89726dd40408d42f0b020a4dac08d115c54 Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Mon, 18 Feb 2019 13:32:34 +0100 Subject: [PATCH] Update track-total-hits.asciidoc Added missing ` --- docs/reference/search/request/track-total-hits.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/search/request/track-total-hits.asciidoc b/docs/reference/search/request/track-total-hits.asciidoc index c416c777366..210f6321816 100644 --- a/docs/reference/search/request/track-total-hits.asciidoc +++ b/docs/reference/search/request/track-total-hits.asciidoc @@ -13,7 +13,7 @@ of hits after a certain threshold. When set to `true` the search response will always track the number of hits that match the query accurately (e.g. `total.relation` will always be equal to `"eq"` -when `track_total_hits is set to true). Otherwise the `"total.relation"` returned +when `track_total_hits` is set to true). Otherwise the `"total.relation"` returned in the `"total"` object in the search response determines how the `"total.value"` should be interpreted. A value of `"gte"` means that the `"total.value"` is a lower bound of the total hits that match the query and a value of `"eq"` indicates @@ -178,4 +178,4 @@ GET twitter/_search <1> The total number of hits is unknown. Finally you can force an accurate count by setting `"track_total_hits"` -to `true` in the request. \ No newline at end of file +to `true` in the request.