You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The parent option is ignored in the delete api (rest only) and for delete actions in the bulk api.
This bug occurs in the case that the _parent field enabled in a mapping, and only the parent option is used. This results in a situation that documents are deleted even if the specified parent value is incorrect.
In the case that routing is required and no routing is specified for a delete request, then the delete is executed on all shards. The also applies when the _parent field is configured on a mapping for a type the delete is executed. The parent id also acts as a routing value.
Current work around is to not use the parent option and just use the routing option, which has the same effect.
…sts.
The `parent` option was ignored in the delete api (rest only) and for delete actions in the bulk api.
This bug occurred in the case that the _parent field is enabled, and only the parent option was used. This resulted in a situation that documents are deleted even if the specified parent value is incorrect.
Closes#3257
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
…sts.
The `parent` option was ignored in the delete api (rest only) and for delete actions in the bulk api.
This bug occurred in the case that the _parent field is enabled, and only the parent option was used. This resulted in a situation that documents are deleted even if the specified parent value is incorrect.
Closeselastic#3257
The
parent
option is ignored in the delete api (rest only) and for delete actions in the bulk api.This bug occurs in the case that the
_parent
field enabled in a mapping, and only theparent
option is used. This results in a situation that documents are deleted even if the specified parent value is incorrect.In the case that routing is required and no routing is specified for a delete request, then the delete is executed on all shards. The also applies when the
_parent
field is configured on a mapping for a type the delete is executed. The parent id also acts as a routing value.Current work around is to not use the
parent
option and just use therouting
option, which has the same effect.Test case:
The text was updated successfully, but these errors were encountered: