anchor.diff:  // TESTRESPONSE[s/0TvkCyF7TAmM1wHP4a42-A/$body.shards.1.0.allocation_id.id/]
   // TESTRESPONSE[s/fMju3hd1QHWmWrIgFnI4Ww/$body.shards.0.0.allocation_id.id/]
   
  -This time the search will only be executed against two of the shards, because
  -routing values have been specified.
  -
  -[float]
  -==== All parameters:
  -
  -[horizontal]
  -`routing`::
  -    A comma-separated list of routing values to take into account when
  -    determining which shards a request would be executed against.
  -
  -`preference`::
  -    Controls a `preference` of which shard replicas to execute the search
  -    request on. By default, the operation is randomized between the shard
  -    replicas. See the link:search-request-body.html#request-body-search-preference[preference]
  -    documentation for a list of all acceptable values.
  -
  -`local`::
  -    A boolean value whether to read the cluster state locally in order to
  -    determine where shards are allocated instead of using the Master node's
  -    cluster state.+The search will only be executed against two of the shards, because outing 
  +values have been specified.
  
positive.code: // TESTRESPONSE[s/bU_KLGJISbW0RejwnwDPKw/$body.shards.3.0.allocation_id.id/]
  // TESTRESPONSE[s/DMs7_giNSwmdqVukF7UydA/$body.shards.4.0.allocation_id.id/]
  
  And specifying the same request, this time with a routing value:
  
  [source,js]
  --------------------------------------------------
  
negative.code: [[search-shards]]
  === Search Shards API
  
  Returns the indices and shards that a search request would be executed against.
  
  [source,js]
  --------------------------------------------------
  