OpenSearch/rest-api-spec/test/index/55_parent_with_routing.yaml

---
"Parent with routing":

 - do:
      indices.create:
          index: test_1
          body:
            mappings:
              test:
                _parent: { type: "foo" }
            settings:
              number_of_replicas: 0

 - do:
      cluster.health:
          wait_for_status: green

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

 - do:
      get:
          index:   test_1
          type:    test
          id:      1
          parent:  5
          routing: 4
          fields:  [_parent, _routing]

 - match:   { _id:      "1"}
 - match:   { fields._parent: "5"}
 - match:   { fields._routing: "4"}

 - do:
      catch: missing
      get:
          index:   test_1
          type:    test
          id:      1
          parent:  5

 - do:
      get:
          index:   test_1
          type:    test
          id:      1
          routing: 4
Fixed tests for info, ping and index 2013-06-26 16:04:20 -04:00			`---`
			`"Parent with routing":`
Renamed "ok" and "not_ok" to "is_true" and "is_false" and tidied up the layout to make it easier to read 2013-07-01 09:58:23 -04:00
Fixed tests for info, ping and index 2013-06-26 16:04:20 -04:00			`- do:`
			`indices.create:`
			`index: test_1`
			`body:`
			`mappings:`
			`test:`
			`_parent: { type: "foo" }`
[TEST] moved routing REST tests to 0 replicas REST tests get run against either 1 node or multiple nodes. Wait for yellow with replicas>0 is not enough when running against multiple nodes as replicas shard might get initialized during testing, which can cause timing issues. 2014-02-10 06:30:37 -05:00			`settings:`
			`number_of_replicas: 0`

Fixed tests for info, ping and index 2013-06-26 16:04:20 -04:00			`- do:`
			`cluster.health:`
[TEST] moved routing REST tests to 0 replicas REST tests get run against either 1 node or multiple nodes. Wait for yellow with replicas>0 is not enough when running against multiple nodes as replicas shard might get initialized during testing, which can cause timing issues. 2014-02-10 06:30:37 -05:00			`wait_for_status: green`
Fixed tests for info, ping and index 2013-06-26 16:04:20 -04:00
			`- do:`
			`index:`
			`index: test_1`
			`type: test`
			`id: 1`
			`parent: 5`
			`routing: 4`
			`body: { foo: bar }`

			`- do:`
			`get:`
			`index: test_1`
			`type: test`
			`id: 1`
			`parent: 5`
			`routing: 4`
			`fields: [_parent, _routing]`
Renamed "ok" and "not_ok" to "is_true" and "is_false" and tidied up the layout to make it easier to read 2013-07-01 09:58:23 -04:00
more numeric ids 2013-07-11 07:52:20 -04:00			`- match: { _id: "1"}`
			`- match: { fields._parent: "5"}`
			`- match: { fields._routing: "4"}`
Fixed tests for info, ping and index 2013-06-26 16:04:20 -04:00
			`- do:`
			`catch: missing`
			`get:`
			`index: test_1`
			`type: test`
			`id: 1`
			`parent: 5`

			`- do:`
			`get:`
			`index: test_1`
			`type: test`
			`id: 1`
			`routing: 4`