From 78c254a9c36fe1093d952036679367673457ae8c Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Wed, 31 Jul 2019 11:47:10 -0700 Subject: [PATCH] [DOCS] Adds notable 7.3 breaking changes (#45057) --- docs/reference/migration/migrate_7_3.asciidoc | 26 +++++++++---------- 1 file changed, 12 insertions(+), 14 deletions(-) diff --git a/docs/reference/migration/migrate_7_3.asciidoc b/docs/reference/migration/migrate_7_3.asciidoc index 93404fb3b67..99e4355a0ab 100644 --- a/docs/reference/migration/migrate_7_3.asciidoc +++ b/docs/reference/migration/migrate_7_3.asciidoc @@ -9,21 +9,17 @@ your application to Elasticsearch 7.3. See also <> and <>. -coming[7.3.0] - //NOTE: The notable-breaking-changes tagged regions are re-used in the //Installation and Upgrade Guide //tag::notable-breaking-changes[] - -// end::notable-breaking-changes[] - +[discrete] [[breaking_73_mapping_changes]] === Mapping changes `dense_vector` field now requires `dims` parameter, specifying the number of dimensions for document and query vectors for this field. -[float] +[discrete] ==== Defining multi-fields within multi-fields Previously, it was possible to define a multi-field within a multi-field. @@ -33,39 +29,41 @@ in 8.0. To resolve the issue, all instances of `fields` that occur within a chained `fields` blocks into a single level, or by switching to `copy_to` if appropriate. +[discrete] [[breaking_73_plugin_changes]] === Plugins changes -[float] +[discrete] ==== IndexStorePlugin changes IndexStore and DirectoryService have been replaced by a stateless and simple DirectoryFactory interface to create custom Lucene directory instances per shard. -[float] +[discrete] [[breaking_73_search_changes]] -=== Search Changes +=== Search changes -[float] +[discrete] ==== Deprecation of queries The `common` query has been deprecated. The same functionality can be achieved by the `match` query if the total number of hits is not tracked. -[float] +[discrete] ===== Deprecation of query parameters The `cutoff_frequency` parameter has been deprecated for `match` and `multi_match` queries. The same functionality can be achieved without any configuration provided that the total number of hits is not tracked. -[float] +[discrete] [[breaking_73_ccr_changes]] -=== CCR Changes +=== CCR changes -[float] +[discrete] ==== Directly modifying aliases of follower indices is no longer allowed Aliases are now replicated to a follower from its leader, so directly modifying aliases on follower indices is no longer allowed. +// end::notable-breaking-changes[] \ No newline at end of file