anchor.diff:  // TEST[setup:twitter]
   
   None of the highlighters built into Elasticsearch care about the order that the
  -fields are highlighted but a plugin may.
  +fields are highlighted but a plugin might.
  
positive.code: // NOTCONSOLE
  ===================================================================
  
  [[phrase-limit]]
  ==== Phrase Limit
  
  WARNING: this is only supported by the `fvh` highlighter
  
  The fast vector highlighter has a `phrase_limit` parameter that prevents
  it from analyzing too many phrases and eating tons of memory.  It defaults
  to 256 so only the first 256 matching phrases in the document scored
  considered.  You can raise the limit with the `phrase_limit` parameter but
  keep in mind that scoring more phrases consumes more time and memory.
  
  If using `matched_fields` keep in mind that `phrase_limit` phrases per
  matched field are considered.
  
  [float]
  [[explicit-field-order]]
  === Field Highlight Order
  Elasticsearch highlights the fields in the order that they are sent.  Per the
  json spec objects are unordered but if you need to be explicit about the order
  that fields are highlighted then you can use an array for `fields` like this:
  [source,js]
  --------------------------------------------------
  GET /_search
  
negative.code: // CONSOLE
  // TEST[setup:twitter]
  
  ===== Specifying a fragmenter for the plain highlighter
  
  When using the `plain` highlighter, you can choose between the `simple` and
  `span` fragmenters:
  
  [source,js]
  --------------------------------------------------
  