anchor.diff:  4. Run a test request
   
   If we have a circuit-breaker error we are trying to do too much in one request and must increase `num_partitions`.
  -If the request was successful but the last account ID in the date-sorted test response was still an account we might want to 
  -expire then we may be missing accounts of interest and have set our numbers too low. We must either 
  +If the request was successful but the last account ID in the date-sorted test response was still an account we might want to
  +expire then we may be missing accounts of interest and have set our numbers too low. We must either
   
   * increase the `size` parameter to return more results per partition (could be heavy on memory) or
   * increase the `num_partitions` to consider less accounts per request (could increase overall processing time as we need to make more requests)
  
positive.code: 
  This shows an error value for each term returned by the aggregation which represents the 'worst case' error in the document count
  and can be useful when deciding on a value for the `shard_size` parameter. This is calculated by summing the document counts for
  the last term returned by all shards which did not return the term. In the example above the error in the document count for Product C
  would be 15 as Shard B was the only shard not to return the term and the document count of the last term it did return was 15.
  The actual document count of Product C was 54 so the document count was only actually off by 4 even though the worst case was that
  it would be off by 15. Product A, however has an error of 0 for its document count, since every shard returned it we can be confident
  that the count returned is accurate.
  
  [source,console-result]
  --------------------------------------------------
  {
      ...
      "aggregations" : {
          "products" : {
              "doc_count_error_upper_bound" : 46,
              "sum_other_doc_count" : 79,
              "buckets" : [
                  {
                      "key" : "Product A",
                      "doc_count" : 100,
                      "doc_count_error_upper_bound" : 0
                  },
                  {
                      "key" : "Product Z",
                      "doc_count" : 52,
                      "doc_count_error_upper_bound" : 2
                  }
                  ...
              ]
          }
      }
  }
  --------------------------------------------------
  // TESTRESPONSE[s/\.\.\.//]
  // TESTRESPONSE[s/: (\-)?[0-9]+/: $body.$_path/]
  
  These errors can only be calculated in this way when the terms are ordered by descending document count. When the aggregation is
  ordered by the terms values themselves (either ascending or descending) there is no error in the document count since if a shard
  
negative.code: 
  There are two error values which can be shown on the terms aggregation. The first gives a value for the aggregation as
  a whole which represents the maximum potential document count for a term which did not make it into the final list of
  terms. This is calculated as the sum of the document count from the last term returned from each shard.
  
  ==== Per bucket document count error
  
  