From ab3fa78ae0a1848abd28c2aed2f096ebd6548c57 Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Mon, 13 Apr 2015 16:35:06 +0200 Subject: [PATCH] Docs: Reverte migration docs mentioning parent removal from update request Relates to #9612 --- docs/reference/migration/migrate_2_0.asciidoc | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/docs/reference/migration/migrate_2_0.asciidoc b/docs/reference/migration/migrate_2_0.asciidoc index d51660a6d37..c37e4222ed6 100644 --- a/docs/reference/migration/migrate_2_0.asciidoc +++ b/docs/reference/migration/migrate_2_0.asciidoc @@ -150,13 +150,7 @@ large, it is recommended to make it replicated to all nodes by setting `index.auto_expand_replicas: 0-all` in order to remove the network overhead as well. -=== Parent parameter on update request - -The `parent` parameter has been removed from the update request. Before 2.x it just set the routing parameter. The -`routing` setting should be used instead. The `parent` setting was confusing, because it had the impression that the parent -a child documents points to can be changed but this is not true. - -==== Delete by query +=== Delete by query The meaning of the `_shards` headers in the delete by query response has changed. Before version 2.0 the `total`, `successful` and `failed` fields in the header are based on the number of primary shards. The failures on replica