OpenSearch/rest-api-spec/test/delete/42_missing_parent.yml

---
"Delete on all shards when parent not specified":

 - do:
      indices.create:
          index: test_1
          body:
            mappings:
              test:
                _parent: { type: "foo" }
 - do:
      cluster.health:
          wait_for_status: yellow

 - do:
      index:
          index:   test_1
          type:    test
          id:      1
          parent:  5
          body:    { foo: bar }

 - do:
      catch:        /routing_missing_exception/
      delete:
          index:   test_1
          type:    test
          id:      1
Added tests for delete 2013-06-28 11:17:23 -04:00			`---`
			`"Delete on all shards when parent not specified":`

			`- do:`
			`indices.create:`
			`index: test_1`
			`body:`
			`mappings:`
			`test:`
			`_parent: { type: "foo" }`
			`- do:`
			`cluster.health:`
			`wait_for_status: yellow`

			`- do:`
			`index:`
			`index: test_1`
			`type: test`
			`id: 1`
			`parent: 5`
			`body: { foo: bar }`

			`- do:`
[REST] Render REST errors in a structural way This commit adds support for structural errors / failures / exceptions on the elasticsearch REST layer. Exceptions are rendering with at least a `type` and a `reason` corresponding to the exception name and the message. Some expcetions like the ones associated with an index or a shard will have additional information about the index the exception was triggered on or the shard respectivly. Each rendered response will also contain a list of root causes which is a list of distinct shard level errors returned for the request. Root causes are the lowest level elasticsearch exception found per shard response and are intended to be displayed to the user to indicate the soruce of the exception. Shard level response are by-default grouped by their type and reason to reduce the amount of duplicates retunred. Yet, the same exception retunred from different indices will not be grouped. Closes #3303 2015-04-24 03:36:10 -04:00			`catch: /routing_missing_exception/`
Added tests for delete 2013-06-28 11:17:23 -04:00			`delete:`
			`index: test_1`
			`type: test`
			`id: 1`