anchor.diff:  }
   --------------------------------------------------
   //CONSOLE
  +
  +<1> `date_range` types accept the same field parameters defined by the <<date, `date`>> type.
  +<2> Example indexing a meeting with 10 to 20 attendees.
  +<3> Date ranges accept the same format as described in <<ranges-on-dates, date range queries>>.
  +<4> Example date range using date time stamp. This also accepts <<date-math, date math>> formatting, or "now" for system time.
   
   The following is an example of a <<query-dsl-term-query, term query>> on the `integer_range` field named "expected_attendees".
   
  
positive.code: // CONSOLE
  // TEST[setup:range_index]
  
  <1> `date_range` types accept the same field parameters defined by the <<date, `date`>> type.
  <2> Example indexing a meeting with 10 to 20 attendees.
  <3> Date ranges accept the same format as described in <<ranges-on-dates, date range queries>>.
  <4> Example date range using date time stamp. This also accepts <<date-math, date math>> formatting, or "now" for system time.
  <5> Range queries work the same as described in <<query-dsl-range-query, range query>>.
  <6> Range queries over range <<mapping-types, fields>> support a `relation` parameter which can be one of `WITHIN`, `CONTAINS`,
      `INTERSECTS` (default).
  
  This query produces a similar result:
  
negative.code: --------------------------------------------------
  // TESTRESPONSE[s/"took": 13/"took" : $body.took/]
  
  The following is an example of a `date_range` query over the `date_range` field named "time_frame".
  
  [source,js]
  