Skip to content

Commit 0234b1f

Browse files
committed
[DOCS] clarify behaviour when routing is required and no routing value is specified
This note in the delete api about broadcasting to all shards is a leftover that should have been removed when the broadcasting feature was removed Relates to #10136
1 parent 3df1478 commit 0234b1f

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

docs/reference/docs/delete.asciidoc

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -56,10 +56,9 @@ The above will delete a tweet with id 1, but will be routed based on the
5656
user. Note, issuing a delete without the correct routing, will cause the
5757
document to not be deleted.
5858

59-
Many times, the routing value is not known when deleting a document. For
60-
those cases, when specifying the `_routing` mapping as `required`, and
61-
no routing value is specified, the delete will be broadcast
62-
automatically to all shards.
59+
When the `_routing` mapping is set as `required` and no routing value is
60+
specified, the delete api will throw a `RoutingMissingException` and reject
61+
the request.
6362

6463
[float]
6564
[[delete-parent]]
@@ -74,6 +73,10 @@ to use the `delete-by-query` plugin to perform a delete on the child
7473
index with the automatically generated (and indexed)
7574
field _parent, which is in the format parent_type#parent_id.
7675

76+
When deleting a child document its parent id must be specified, otherwise
77+
the delete request will be rejected and a `RoutingMissingException` will be
78+
thrown instead.
79+
7780
[float]
7881
[[delete-index-creation]]
7982
=== Automatic index creation

0 commit comments

Comments
 (0)