anchor.diff:  
   The above will sort the countries buckets based on the average height among the female population.
   
  -==== Minimum document count 
  +==== Minimum document count
   
   It is possible to only return terms that match more than a configured number of hits using the `min_doc_count` option:
   
  
positive.code: |=========================================================
  |    | Shard A        | Shard B        | Shard C
  
  | 1  | Product A (25) | Product A (30) | Product A (45) 
  | 2  | Product B (18) | Product B (25) | Product C (44) 
  | 3  | Product C (6)  | Product F (17) | Product Z (36) 
  | 4  | Product D (3)  | Product Z (16) | Product G (30) 
  | 5  | Product E (2)  | Product G (15) | Product E (29) 
  
  |=========================================================
  
  Taking the top 5 results from each of the shards (as requested) and combining them to make a final top 5 list produces 
  the following:
  
  [width="40%",cols="^2,^2"]
  |=========================================================
  
  | 1  | Product A (100) 
  | 2  | Product Z (52) 
  | 3  | Product C (50) 
  | 4  | Product G (45) 
  | 5  | Product B (43) 
  
  |=========================================================
  
  Because Product A was returned from all shards we know that its document count value is accurate. Product C was only 
  returned by shards A and C so its document count is shown as 50 but this is not an accurate count. Product C exists on 
  shard B, but its count of 4 was not high enough to put Product C into the top 5 list for that shard. Product Z was also 
  returned only by 2 shards but the third shard does not contain the term. There is no way of knowing, at the point of 
  combining the results to produce the final list of terms, that there is an error in the document count for Product C and 
  not for Product Z. Product H has a document count of 44 across all 3 shards but was not included in the final list of 
  terms because it did not make it into the top five terms on any of the shards.
  
  ==== Shard Size
  
  The higher the requested `size` is, the more accurate the results will be, but also, the more expensive it will be to
  compute the final results (both due to bigger priority queues that are managed on a shard level and due to bigger data
  transfers between the nodes and the client). 
  
  The `shard_size` parameter can be  used to minimize the extra work that comes with bigger requested `size`. When defined,
  it will determine how many terms the coordinating node will request from each shard. Once all the shards responded, the
  
negative.code: http://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html#UNICODE_CHARACTER_CLASS[`UNICODE_CHARACTER_CLASS`] and
  http://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html#UNIX_LINES[`UNIX_LINES`]
  
  ==== Multi-field terms aggregation
  
  The `terms` aggregation does not support collecting terms from multiple fields
  in the same document.  The reason is that the `terms` agg doesn't collect the
  string term values themselves, but rather uses
  <<search-aggregations-bucket-terms-aggregation-execution-hint,global ordinals>>
  to produce a list of all of the unique values in the field.  Global ordinals
  results in an important performance boost which would not be possible across
  multiple fields.
  
  There are two approaches that you can use to perform a `terms` agg across
  multiple fields:
  
  <<search-aggregations-bucket-terms-aggregation-script,Script>>::
  
  Use a script to retrieve terms from multiple fields.  This disables the global
  ordinals optimization and will be slower than collecting terms from a single
  field, but it gives you the flexibility to implement this option at search
  time.
  
  <<copy-to,`copy_to` field>>::
  
  If you know ahead of time that you want to collect the terms from two or more
  fields, then use `copy_to` in your mapping to create a new dedicated field at
  index time which contains the values from both fields.  You can aggregate on
  this single field, which will benefit from the global ordinals optimization.
  
  ==== Collect mode
  
  added[1.3.0] Deferring calculation of child aggregations
  