anchor.diff:  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`]
   
  -==== Execution hint
  +===== Execution hint
   
   There are two mechanisms by which terms aggregations can be executed: either by using field values directly in order to aggregate
   data per-bucket (`map`), or by using ordinals of the field values instead of the values themselves (`ordinals`). Although the
  
positive.code: **********************************
  
  
  
  === Use on free-text fields
  
  The significant_terms aggregation can be used effectively on tokenized free-text fields to suggest:
  
  
negative.code:          default value of 3 is used to provide a minimum weight-of-evidence.
  
  
  ===== Filtering Values
  
  It is possible (although rarely required) to filter the values for which buckets will be created. This can be done using the `include` and
  `exclude` parameters which are based on regular expressions. This functionality mirrors the features
  