[Docs] Fix badly escaped keywords in migrate_7_0/search.asciidoc (#36964)

This commit is contained in:
Damien Alexandre 2018-12-27 09:18:28 +01:00 committed by Jim Ferenczi
parent 48b0908fc6
commit 47f0a47f3d
1 changed files with 5 additions and 4 deletions

View File

@ -174,9 +174,10 @@ major version.
==== `hits.total` is now an object in the search response
The total hits that match the search request is now returned as an object
with a `value` and a `relation`. `value indicates the number of hits that
match and `relation indicates whether the value is accurate (`eq`) or a lower bound
with a `value` and a `relation`. `value` indicates the number of hits that
match and `relation` indicates whether the value is accurate (`eq`) or a lower bound
(`gte`):
```
{
"hits": {
@ -200,7 +201,7 @@ will be removed in the next major version (8.0).
[float]
==== `hits.total` is omitted in the response if `track_total_hits` is disabled (false)
If `track_total_hits` is set to `false in the search request the search response
If `track_total_hits` is set to `false` in the search request the search response
will set `hits.total` to null and the object will not be displayed in the rest
layer. You can add `rest_total_hits_as_int=true` in the search request parameters
to get the old format back (`"total": -1`).
to get the old format back (`"total": -1`).