anchor.diff:  --------------------------------------------------
   // TESTRESPONSE[s/\.\.\.//]
   
  -<1> The last composite bucket returned by the query.
  -
  -NOTE: The `after_key` is equals to the last bucket returned in the response before
  -any filtering that could be done by <<search-aggregations-pipeline, Pipeline aggregations>>.
  -If all buckets are filtered/removed by a pipeline aggregation, the `after_key` will contain
  -the last bucket before filtering.
  -
  -The `after` parameter can be used to retrieve the composite buckets that are **after**
  -the last composite buckets returned in a previous round.
  -For the example below the last bucket can be found in `after_key` and the next
  -round of result can be retrieved with:
  +To get the next set of buckets, resend the same aggregation with the `after`
  +parameter set to the `after_key` value returned in the response.
  +For example, this request uses the `after_key` value provided in the previous response:
   
   [source,console,id=composite-aggregation-after-example]
   --------------------------------------------------
  
positive.code: --------------------------------------------------
  
  <1> Should restrict the aggregation to buckets that sort **after** the provided values.
  
  ==== Early termination
  
  
negative.code:     ...
      "aggregations": {
          "my_buckets": {
              "after_key": {
                  "date": 1494288000000,
                  "product": "mad max"
              },
  