anchor.diff:  // NOTCONSOLE
   
   [float]
  -=== Use `include_type_name=false` to prepare for upgrade to 8.0
  -
  -Index creation and mapping APIs support a new `include_type_name` url parameter 
  -starting with version 6.7. It will default to `true` in version 6.7, default to
  -`false` in version 7.0 and will be removed in version 8.0. When set to `true`, 
  -this parameter enables the pre-7.0 behavior of using type names in the API.
  -
  -See some examples of interactions with Elasticsearch with this option turned off:
  -
  -[float]
  -==== Index creation
  +=== Typeless APIs in 7.0
  +
  +In Elasticsearch 7.0, each API will support typeless requests,
  +and specifying a type will produce a deprecation warning.
  +
  +NOTE: Typeless APIs work even if the target index contains a custom type.
  +For example, if an index has the the custom type name `my_type`, we can add
  +documents to it using typeless `index` calls, and load documents with typeless
  +`get` calls.
  +
  +[float]
  +==== Indices APIs
  +
  +Index creation, index template, and mapping APIs support a new `include_type_name`
  +url parameter that specifies whether mapping definitions in requests and responses
  +should contain the type name. The parameter defaults to `true` in version 6.7 to
  +match the pre-7.0 behavior of using type names in mappings. It defaults to `false`
  +in version 7.0 and will be removed in version 8.0.
  +
  +See some examples of interactions with Elasticsearch with this option provided:
   
   [source,js]
   --------------------------------------------------
  
positive.code: // CONSOLE
  <1> Mappings are included directly under the `mappings` key, without a type name.
  
  [float]
  ==== PUT and GET mappings
  
  [source,js]
  --------------------------------------------------
  PUT index
  
  PUT index/_mappings?include_type_name=false
  {
    "properties": { <1>
      "foo": {
        "type": "keyword"
      }
    }
  }
  
  GET index/_mappings?include_type_name=false
  --------------------------------------------------
  // CONSOLE
  <1> Mappings are included directly under the `mappings` key, without a type name.
  
  
  The above call returns
  
  
negative.code: an index that doesn't exist yet, the template is always honored. This is
  usually not a problem due to the fact that typeless index calls work on typed
  indices.
  
  [float]
  ==== Mixed-version clusters
  
  In a cluster composed of both 6.7 and 7.0 nodes, the parameter
  `include_type_name` should be specified in indices APIs like index
  creation. This is because the parameter has a different default between
  6.7 and 7.0, so the same mapping definition will not be valid for both
  node versions.
  
  Typeless document APIs such as `bulk` and `update` are only available as of
  7.0, and will not work with 6.7 nodes. This also holds true for the typeless
  versions of queries that perform document lookups, such as `terms`.
  