Skip to content

Commit 73d0a1b

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 920a21e commit 73d0a1b

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
@@ -57,10 +57,9 @@ The above will delete a tweet with id 1, but will be routed based on the
5757
user. Note, issuing a delete without the correct routing, will cause the
5858
document to not be deleted.
5959

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

6564
[float]
6665
[[delete-parent]]
@@ -75,6 +74,10 @@ to use the <<docs-delete-by-query,Delete By Query API>> to perform a
7574
index with the automatically generated (and indexed)
7675
field _parent, which is in the format parent_type#parent_id.
7776

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

0 commit comments

Comments
 (0)