anchor.diff:  ==== `collectors` Section
   
   The Collectors portion of the response shows high-level execution details. Lucene works by defining a "Collector"
  -which is responsible for coordinating the traversal, scoring and collection of matching documents.  Collectors
  +which is responsible for coordinating the traversal, scoring, and collection of matching documents.  Collectors
   are also how a single query can record aggregation results, execute unscoped "global" queries, execute post-query
   filters, etc.
   
  
positive.code: 
  ==== Understanding MultiTermQuery output
  
  A special note needs to be made about the `MultiTermQuery` class of queries.  This includes wildcards, regex and fuzzy
  queries.  These queries emit very verbose responses, and are not overly structured.
  
  Essentially, these queries rewrite themselves on a per-segment basis.  If you imagine the wildcard query `b*`, it technically
  can match any token that begins with the letter "b".  It would be impossible to enumerate all possible combinations,
  so Lucene rewrites the query in context of the segment being evaluated.  E.g. one segment may contain the tokens
  `[bar, baz]`, so the query rewrites to a BooleanQuery combination of "bar" and "baz".  Another segment may only have the
  token `[bakery]`, so query rewrites to a single TermQuery for "bakery".
  
  Due to this dynamic, per-segment rewriting, the clean tree structure becomes distorted and no longer follows a clean
  "lineage" showing how one query rewrites into the next.  At present time, all we can do is apologize, and suggest you
  
negative.code: // TEST[s/_search/_search\?filter_path=profile.shards.aggregations/]
  // TEST[continued]
  
  This yields the following aggregation profile output:
  
  [source,js]
  --------------------------------------------------
  