anchor.diff:  --------------------------------------------------
   
   .Additional supported query string options
  -* `routing` - In the case the percolate queries are partitioned by a custom routing value, that routing option make sure
  +* `routing` - In case the percolate queries are partitioned by a custom routing value, that routing option makes sure
   that the percolate request only gets executed on the shard where the routing value is partitioned to. This means that
   the percolate request only gets executed on one shard instead of all shards. Multiple values can be specified as a
   comma separated string, in that case the request can be be executed on more than one shard.
  
positive.code: At percolate time the document specified in the request gets parsed into a Lucene document and is stored in a in-memory
  Lucene index. This in-memory index can just hold this one document and it is optimized for that. Then all the queries
  that are registered to the index that the percolate request is targeted for are going to be executed on this single document
  in-memory index. This happens on each shard the percolate request need to execute.
  
  By using `routing`, `filter` or `query` features the amount of queries that need to be executed can be reduced and thus
  the time the percolate api needs to run can be decreased.
  
negative.code: }
  --------------------------------------------------
  
  On top of this also a mapping type can be associated with this query. This allows to control how certain queries
  like range queries, shape filters and other query & filters that rely on mapping settings get constructed. This is
  important since the percolate queries are indexed into the `.percolator` type, and the queries / filters that rely on
  mapping settings would yield unexpected behaviour. Note by default field names do get resolved in a smart manner,
  