anchor.diff:  --------------------------------------------------
   // CONSOLE
   // TEST[continued]
  -
  -Dissecting the above, the bool query contains a `match_all` query (the query part) and a `range` query (the filter part). We can substitute any other queries into the query and the filter parts. In the above case, the range query makes perfect sense since documents falling into the range all match "equally", i.e., no document is more relevant than another.
  -
  -In addition to the `match_all`, `match`, `bool`, and `range` queries, there are a lot of other query types that are available and we won't go into them here. Since we already have a basic understanding of how they work, it shouldn't be too difficult to apply this knowledge in learning and experimenting with the other query types.
   
   [[getting-started-aggregations]]
   == Analyze results with aggregations
  
positive.code: // TESTRESPONSE[s/"took" : 63/"took" : $body.took/]
  // TESTRESPONSE[s/\.\.\./$body.hits.hits.2, $body.hits.hits.3, $body.hits.hits.4, $body.hits.hits.5, $body.hits.hits.6, $body.hits.hits.7, $body.hits.hits.8, $body.hits.hits.9/]
  
  As for the response, we see the following parts:
  
  * `took` – time in milliseconds for Elasticsearch to execute the search
  * `timed_out` – tells us if the search timed out or not
  * `_shards` – tells us how many shards were searched, as well as a count of the successful/failed searched shards
  * `hits` – search results
  * `hits.total` – an object that contains information about the total number of documents matching our search criteria
  ** `hits.total.value` - the value of the total hit count (must be interpreted in the context of `hits.total.relation`).
  ** `hits.total.relation` - whether `hits.total.value` is the exact hit count, in which case it is equal to `"eq"` or a
                             lower bound of the total hit count (greater than or equals), in which case it is equal to `gte`.
  * `hits.hits` – actual array of search results (defaults to first 10 documents)
  * `hits.sort` - sort value of the sort key for each result (missing if sorting by score)
  * `hits._score` and `max_score` - ignore these fields for now
  
  The accuracy of `hits.total` is controlled by the request parameter `track_total_hits`, when set to true
  the request will track the total hits accurately (`"relation": "eq"`). It defaults to `10,000`
  which means that the total hit count is accurately tracked up to `10,000` documents.
  You can force an accurate count by setting `track_total_hits` to true explicitly.
  See the <<request-body-search-track-total-hits, request body>> documentation
  for more details.
  
  Here is the same exact search above using the alternative request body method:
  
  [source,js]
  --------------------------------------------------
  
negative.code: // CONSOLE
  // TEST[continued]
  
  To perform a phrase search rather than matching individual terms, you use
  `match_phrase` instead of `match`. For example, the following request only 
  matches addresses that contain the phrase `mill lane`: 
  
  [source,js]
  --------------------------------------------------
  