Parcourir la source

[DOCS] Remove `include_type_name` query parameter (#78394)

Adds an 8.0 breaking change for PR #48632.
James Rodewig il y a 4 ans
Parent
commit
f4b5ef7416
1 fichiers modifiés avec 14 ajouts et 1 suppressions
  1. 14 1
      docs/reference/migration/migrate_8_0/mappings.asciidoc

+ 14 - 1
docs/reference/migration/migrate_8_0/mappings.asciidoc

@@ -18,7 +18,6 @@ Use a maximum of 10 completion contexts in a completion field. Specifying more
 than 10 completion contexts will return an error.
 ====
 
-
 .Mapping API endpoints containing mapping types have been removed.
 [%collapsible]
 ====
@@ -108,4 +107,18 @@ These parameters have been removed in 8.0.0.
 In 8.0, you can no longer create mappings that include these parameters.
 However, 7.x indices that use these mapping parameters will continue to work.
 ====
+
+.The `include_type_name` query parameter has been removed.
+[%collapsible]
+====
+*Details* +
+The `include_type_name` query parameter has been removed from the index
+creation, index template, and mapping APIs. Previously, you could set
+`include_type_name` to `true` to indicate that requests and responses should
+include a mapping type name. Mapping types have been removed in 8.x.
+
+*Impact* +
+Discontinue use of the `include_type_name` query parameter. Requests that
+include the parameter will return an error.
+====
 // end::notable-breaking-changes[]