anchor.diff:  --------------------------------------------------
   // CONSOLE
   
  -And this example return only `blocks` data:
  +Finally, this example return only the `blocks` metadata:
  +
   [source,js]
   --------------------------------------------------
   GET /_cluster/state/blocks
  
positive.code: --------------------------------------------------
  // CONSOLE
  
  The response provides the cluster name, the total compressed size
  of the cluster state (its size when serialized for transmission over
  the network), and the cluster state itself, which can be filtered to
  only retrieve the parts of interest, as described below.
  
  The cluster's `cluster_uuid` is also returned as part of the top-level
  response, in addition to the `metadata` section. added[6.4.0]
  
  NOTE: While the cluster is still forming, it is possible for the `cluster_uuid`
        to be `_na_` as well as the cluster state's version to be `-1`.
  
  By default, the cluster state request is routed to the master node, to
  ensure that the latest cluster state is returned.   
  For debugging purposes, you can retrieve the cluster state local to a
  particular node by adding `local=true` to the  query string.
  
  [float]
  === Response Filters
  
  As the cluster state can grow (depending on the number of shards and indices, your mapping, templates),
  it is possible to filter the cluster state response specifying the parts in the URL.
  
  [source,js]
  --------------------------------------------------
  GET /_cluster/state/{metrics}/{indices}
  --------------------------------------------------
  // CONSOLE
  
  `metrics` can be a comma-separated list of
  
  `version`::
      Shows the cluster state version.
  
negative.code: [[cluster-state]]
  == Cluster State
  
  The cluster state API allows access to metadata representing the state of the
  whole cluster. This includes information such as
  
  * the set of nodes in the cluster
  
  * all cluster-level settings
  
  * information about the indices in the cluster, including their mappings and
    settings
  
  * the locations of all the shards in the cluster
  
  The response is an internal representation of the cluster state and its format
  may change from version to version. If possible, you should obtain any
  information from the cluster state using the other, more stable,
  <<cluster,cluster APIs>>.
  
  [source,js]
  --------------------------------------------------
  