From 85848af8cf94170104b9396970165027b5b0e6a9 Mon Sep 17 00:00:00 2001 From: lcawl Date: Thu, 28 Mar 2019 10:03:40 -0700 Subject: [PATCH] [DOCS] Fixes formatting in breaking changes --- docs/reference/migration/migrate_7_0/search.asciidoc | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/reference/migration/migrate_7_0/search.asciidoc b/docs/reference/migration/migrate_7_0/search.asciidoc index cf3342ea7ee..f2c3d4d397a 100644 --- a/docs/reference/migration/migrate_7_0/search.asciidoc +++ b/docs/reference/migration/migrate_7_0/search.asciidoc @@ -213,19 +213,21 @@ 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`): -``` +[source,js] +-------------------------------------------------- { "hits": { - "total": { <1> + "total": { "value": 1000, "relation": "eq" }, ... } } -``` +-------------------------------------------------- +// NOTCONSOLE -The "total" object in the response indicates that the query matches exactly 1000 +The `total` object in the response indicates that the query matches exactly 1000 documents ("eq"). The `value` is always accurate (`"relation": "eq"`) when `track_total_hits` is set to true in the request. You can also retrieve `hits.total` as a number in the rest response by adding