[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
This commit is contained in:
javanna 2016-08-08 10:41:59 +02:00 committed by Luca Cavanna
parent 920a21e55c
commit 73d0a1b777
1 changed files with 7 additions and 4 deletions

View File

@ -57,10 +57,9 @@ The above will delete a tweet with id 1, but will be routed based on the
user. Note, issuing a delete without the correct routing, will cause the
document to not be deleted.
Many times, the routing value is not known when deleting a document. For
those cases, when specifying the `_routing` mapping as `required`, and
no routing value is specified, the delete will be broadcast
automatically to all shards.
When the `_routing` mapping is set as `required` and no routing value is
specified, the delete api will throw a `RoutingMissingException` and reject
the request.
[float]
[[delete-parent]]
@ -75,6 +74,10 @@ to use the <<docs-delete-by-query,Delete By Query API>> to perform a
index with the automatically generated (and indexed)
field _parent, which is in the format parent_type#parent_id.
When deleting a child document its parent id must be specified, otherwise
the delete request will be rejected and a `RoutingMissingException` will be
thrown instead.
[float]
[[delete-index-creation]]
=== Automatic index creation