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/index/11_shard_header.yaml

31 lines
623 B
YAML
Raw Normal View History

Core: Added `_shards` header to all write responses. The header indicates to how many shard copies (primary and replicas shards) a write was supposed to go to, to how many shard copies to write succeeded and potentially captures shard failures if writing into a replica shard fails. For async writes it also includes the number of shards a write is still pending. Closes #7994
2014-09-24 08:54:50 -04:00
---
"Index check shard header":
- do:
indices.create:
Test: Only run the test that verifies the `pending` field in the `_shards` header if the test cluster has two are more data nodes.
2015-01-12 04:29:23 -05:00
index: foobar
Core: Added `_shards` header to all write responses. The header indicates to how many shard copies (primary and replicas shards) a write was supposed to go to, to how many shard copies to write succeeded and potentially captures shard failures if writing into a replica shard fails. For async writes it also includes the number of shards a write is still pending. Closes #7994
2014-09-24 08:54:50 -04:00
body:
settings:
number_of_shards: "1"
number_of_replicas: "0"
- do:
cluster.health:
wait_for_status: green
- do:
index:
Test: Only run the test that verifies the `pending` field in the `_shards` header if the test cluster has two are more data nodes.
2015-01-12 04:29:23 -05:00
index: foobar
Core: Added `_shards` header to all write responses. The header indicates to how many shard copies (primary and replicas shards) a write was supposed to go to, to how many shard copies to write succeeded and potentially captures shard failures if writing into a replica shard fails. For async writes it also includes the number of shards a write is still pending. Closes #7994
2014-09-24 08:54:50 -04:00
type: baz
id: 1
body: { foo: bar }
Test: Only run the test that verifies the `pending` field in the `_shards` header if the test cluster has two are more data nodes.
2015-01-12 04:29:23 -05:00
- match: { _index: foobar }
Core: Added `_shards` header to all write responses. The header indicates to how many shard copies (primary and replicas shards) a write was supposed to go to, to how many shard copies to write succeeded and potentially captures shard failures if writing into a replica shard fails. For async writes it also includes the number of shards a write is still pending. Closes #7994
2014-09-24 08:54:50 -04:00
- match: { _type: baz }
- match: { _id: "1"}
- match: { _version: 1}
- match: { _shards.total: 1}
- match: { _shards.successful: 1}
- match: { _shards.failed: 0}
- is_false: _shards.pending