javanna 4348959f9d Delete api: remove broadcast delete if routing is missing when required ... This commit changes the behaviour of the delete api when processing a delete request that refers to a type that has routing set to required in the mapping, and the routing is missing in the request. Up until now the delete api sent a broadcast delete request to all of the shards that belong to the index, making sure that the document could be found although the routing value wasn't specified. This was probably not the best choice: if the routing is set to required, an error should be thrown instead. A `RoutingMissingException` gets now thrown instead, like it happens in the same situation with every other api (index, update, get etc.). Last but not least, this change allows to get rid of a couple of `TransportAction`s, `Request`s and `Response`s and simplify the codebase. Closes #9123 Closes #10136		2015-03-20 09:19:43 +01:00
..
index.asciidoc	Docs: Changed breaking docs in master to correspond with 1.x for easier merging	2014-11-13 13:50:57 +01:00
migrate_1_0.asciidoc	Docs: Fixed some deleted refs	2014-09-26 21:35:57 +02:00
migrate_1_4.asciidoc	Docs: Fixed a bad ref to docs-bulk-udp which no longer exists in master	2014-11-13 14:34:49 +01:00
migrate_2_0.asciidoc	Delete api: remove broadcast delete if routing is missing when required	2015-03-20 09:19:43 +01:00