Browse Source

Fix up docs for #78876 (#80580)

Follow-up to #78876 to rework the deprecation docs slightly.
David Turner 3 years ago
parent
commit
f9afa8750f
1 changed files with 12 additions and 7 deletions
  1. 12 7
      docs/reference/migration/migrate_8_1.asciidoc

+ 12 - 7
docs/reference/migration/migrate_8_1.asciidoc

@@ -58,26 +58,31 @@ enable <<deprecation-logging, deprecation logging>>.
 [%collapsible]
 ====
 *Details* +
-Legacy values for the `discovery.type` setting are deprecated and will be forbidden in a future version.
+Legacy values for the `discovery.type` setting are deprecated and will be
+forbidden in a future version.
 
 *Impact* +
 Do not set `discovery.type` to any value except `single-node` or `multi-node`.
 All other values are equivalent to the default discovery type which is
-`multi-node`.
-Where possible, omit this setting so that {es} uses the default discovery type.
+`multi-node`. Where possible, omit this setting so that {es} uses the default
+discovery type.
 ====
 
 [discrete]
-[[breaking_8.1_lenient_bulk_action_deprecation]]
-==== Lenient parsing of bulk actions
+[[breaking_8.1_crud_deprecation]]
+==== CRUD deprecations
 
 [[deprecate-lenient-parsing-of-bulk-actions]]
 .Lenient parsing of bulk actions is deprecated.
 [%collapsible]
 ====
 *Details* +
-{es} 8.1 parses bulk actions more strictly in order to make sure there are no arbitrary fields after a bulk action declaration and that it gets properly closed with the closing brace.
+Older versions of {es} parse the action lines of bulk requests very permissively
+and would silently ignore invalid or malformed actions. This lenience is
+deprecated and a future version will reject bulk requests containing invalid
+actions.
 
 *Impact* +
-Make sure your bulk actions are valid JSON objects and that you don't have any arbitrary JSON fields after bulk actions.
+Ensure that bulk actions are well-formed JSON objects containing a single entry
+with the correct key.
 ====