anchor.diff:  // CONSOLE
   // TEST[setup:twitter]
   
  -And here is a sample response:
  +
  +[[search-request-body-api-request]]
  +==== {api-request-title}
  +
  +
  +`GET /<index>/_search
  +{
  +  "query": {<parameters>}
  +}`
  +
  +
  +[[search-request-body-api-desc]]
  +==== {api-description-title}
  +
  +The search request can be executed with a search DSL, which includes the
  +<<query-dsl,Query DSL>>, within its body.
  +
  +
  +[[search-request-body-api-path-params]]
  +==== {api-path-parms-title}
  +
  +include::{docdir}/rest-api/common-parms.asciidoc[tag=index]
  +
  +
  +[[search-request-body-api-request-body]]
  +==== {api-request-body-title}
  +
  +`allow_partial_search_results`:: 
  +  (Optional, boolean) Set to `false` to fail the request if only partial results 
  +  are available. Defaults to `true`, which returns partial results in the event 
  +  of timeouts or partial failures You can override the default behavior for all 
  +  requests by setting `search.default_allow_partial_results` to `false` in the 
  +  cluster settings.
  +
  +`batched_reduce_size`:: 
  +  (Optional, integer) The number of shard results that should be reduced at once 
  +  on the coordinating node. This value should be used as a protection mechanism 
  +  to reduce the memory overhead per search request if the potential number of 
  +  shards in the request can be large.
  +
  +[[ccs-minimize-roundtrips]]
  +`ccs_minimize_roundtrips`::
  +  (Optional, boolean) If `true`, the network round-trips between the 
  +  coordinating node and the remote clusters ewill be minimized when executing 
  +  {ccs} requests. See <<ccs-reduction>> for more. Defaults to `true`. 
  +
  +include::{docdir}/rest-api/common-parms.asciidoc[tag=from]
  +
  +`request_cache`::
  +  (Optional, boolean) If `true`, the caching of search results is enabled for 
  +  requests where `size` is `0`. See <<shard-request-cache>>.
  +
  +include::{docdir}/rest-api/common-parms.asciidoc[tag=search_type]
  +
  +`size`:: 
  +  (Optional, integer) The number of hits to return. Defaults to `10`.
  +
  +include::{docdir}/rest-api/common-parms.asciidoc[tag=terminate_after]
  +
  +include::{docdir}/rest-api/common-parms.asciidoc[tag=timeout]
  +
  +
  +Out of the above, the `search_type`, `request_cache` and the 
  +`allow_partial_search_results` settings must be passed as query-string 
  +parameters. The rest of the search request should be passed within the body 
  +itself. The body content can also be passed as a REST parameter named `source`.
  +
  +Both HTTP GET and HTTP POST can be used to execute search with body. Since not
  +all clients support GET with body, POST is allowed as well.
  +
  +
  +[[search-request-body-api-example]]
  +==== {api-examples-title}
  +
  +[source,js]
  +--------------------------------------------------
  +GET /twitter/_search
  +{
  +    "query" : {
  +        "term" : { "user" : "kimchy" }
  +    }
  +}
  +--------------------------------------------------
  +// CONSOLE
  +// TEST[setup:twitter]
  +
  +
  +The API returns the following response:
   
   [source,js]
   --------------------------------------------------
  
positive.code: --------------------------------------------------
  // TESTRESPONSE[s/"took": 3/"took": $body.took/]
  
  The `took` time in the response contains the milliseconds that this request
  took for processing, beginning quickly after the node received the query, up
  until all search related work is done and before the above JSON is returned
  
negative.code: --------------------------------------------------
  // CONSOLE
  // TEST[setup:twitter]
  
  
  The response will not contain any hits as the `size` was set to `0`. The
  `hits.total` will be either equal to `0`, indicating that there were no
  