honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/rest-api-spec/test/get/55_parent_with_routing.yaml

56 lines
1003 B
YAML
Raw Normal View History

Added tests for get
2013-06-27 05:34:24 -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
Added tests for get
2013-06-27 05:34:24 -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:
[TEST] Replaced RestTestSuiteRunner with parametrized test that uses RandomizedRunner directly ElasticsearchRestTests extends now ElasticsearchIntegrationTest and makes use of our ordinary test infrastructure, in particular all randomized aspects now come for free instead of having to maintain a separate (custom) tests runner We previously parsed only the tests that needed to be run given the version of the cluster the tests are running against. This doesn't happen anymore as it didn't buy much and it would be harder to support as the tests get now parsed before the test cluster gets started. Thus all the tests are now parsed regardless of their skip sections, afterwards the ones that don't need to be run will be skipped through assume directives. Fixed REST tests that rely on a specific number of shards as this change introduces also random number of shards and replicas (through randomIndexTemplate) Closes #5654
2014-03-10 08:48:17 -04:00
number_of_shards: 5
[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
number_of_replicas: 0
Added tests for get
2013-06-27 05:34:24 -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
Added tests for get
2013-06-27 05:34:24 -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
text ids
2013-07-10 20:21:56 -04:00
- match: { _id: "1"}
Rest: Add all meta fields to the top level json document. Some of our meta fields (such as _id, _version, ...) are returned as top-level properties of the json document, while other properties (_timestamp, _routing, ...) are returned under `fields`. This commit makes all meta fields returned as top-level properties. So eg. `GET test/test/1?fields=_timestamp,foo` would now return ```json { "_index": "test", "_type": "test", "_id": "1", "_version": 1, "_timestamp": 10000000, "found": true, "fields": { "foo": [ "bar" ] } } ``` while it used to return ```json { "_index": "test", "_type": "test", "_id": "1", "_version": 1, "found": true, "fields": { "_timestamp": 10000000, "foo": [ "bar" ] } } ```
2014-10-17 06:35:20 -04:00
- match: { _parent: "5"}
- match: { _routing: "4"}
Added tests for get
2013-06-27 05:34:24 -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