anchor.diff:  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.
  +in-memory index. This happens on each shard the percolate request needs 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.
  
positive.code: === Dedicated percolator index
  
  Percolate queries can be added to any index. Instead of adding percolate queries to the index the data resides in,
  these queries can also be added to an dedicated index. The advantage of this is that this dedicated percolator index
  can have its own index settings (For example the number of primary and replicas shards). If you choose to have a dedicated
  percolate index, you need to make sure that the mappings from the normal index are also available on the percolate index.
  Otherwise percolate queries can be parsed incorrectly.
  
negative.code: --------------------------------------------------
  
  .Additional supported query string options
  * `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.
  