anchor.diff:  ---------------------------------
   // TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
   
  -If a `time_zone` of `-01:00` is specified, then midnight starts at one hour before
  -midnight UTC:
  +If you specify a `time_zone` of `-01:00`, midnight in that timezone is one hour
  +before midnight UTC:
   
   [source,js]
   ---------------------------------
  
positive.code: --------------------------------------------------
  // TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
  
  The response will contain all the buckets having as key the relative day of
  the week: 1 for Monday, 2 for Tuesday... 7 for Sunday.
  
negative.code: --------------------------------------------------
  // TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
  
  ===== Scripts
  
  As with the normal <<search-aggregations-bucket-histogram-aggregation,histogram>>,
  both document-level scripts and
  value-level scripts are supported. You can control the order of the returned
  buckets using the `order`
  settings and filter the returned buckets based on a `min_doc_count` setting
  (by default all buckets between the first
  bucket that matches documents and the last one are returned). This histogram
  also supports the `extended_bounds`
  setting, which enables extending the bounds of the histogram beyond the data
  itself. For more information, see
  <<search-aggregations-bucket-histogram-aggregation-extended-bounds,`Extended Bounds`>>.
  
  ===== Missing value
  
  The `missing` parameter defines how to treat documents that are missing a value.
  By default, they are ignored, but it is also possible to treat them as if they
  have a value.
  
  [source,js]
  --------------------------------------------------
  