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/indices.open/20_multiple_indices.yaml

93 lines
1.3 KiB
YAML
Raw Normal View History

Fixed open/close index api when using wildcard only Named wildcards were not always properly replaced with proper values by PathTrie. Delete index (curl -XDELETE localhost:9200/*) worked anyway as the named wildcard is the last path element (and even if {index} didn't get replaced with '*', the empty string would have mapped to all indices anyway). When the named wildcard wasn't the last path element (e.g. curl -XPOST localhost:29200/*/_close), the variable didn't get replaced with the current '*' value, but with the empty string, which leads to an error as empty index is not allowed by open/close index. Closes #4564
2013-12-24 09:29:59 -05:00
setup:
- do:
indices.create:
index: test_index1
[TEST] indices.open REST tests need 0 replicas With replicas the search requests might go to shards that are not ready, since we have a wait for yellow. We can now switch to wait for green as well.
2014-05-22 04:55:57 -04:00
body:
settings:
number_of_replicas: 0
Fixed open/close index api when using wildcard only Named wildcards were not always properly replaced with proper values by PathTrie. Delete index (curl -XDELETE localhost:9200/*) worked anyway as the named wildcard is the last path element (and even if {index} didn't get replaced with '*', the empty string would have mapped to all indices anyway). When the named wildcard wasn't the last path element (e.g. curl -XPOST localhost:29200/*/_close), the variable didn't get replaced with the current '*' value, but with the empty string, which leads to an error as empty index is not allowed by open/close index. Closes #4564
2013-12-24 09:29:59 -05:00
- do:
indices.create:
index: test_index2
[TEST] indices.open REST tests need 0 replicas With replicas the search requests might go to shards that are not ready, since we have a wait for yellow. We can now switch to wait for green as well.
2014-05-22 04:55:57 -04:00
body:
settings:
number_of_replicas: 0
Fixed open/close index api when using wildcard only Named wildcards were not always properly replaced with proper values by PathTrie. Delete index (curl -XDELETE localhost:9200/*) worked anyway as the named wildcard is the last path element (and even if {index} didn't get replaced with '*', the empty string would have mapped to all indices anyway). When the named wildcard wasn't the last path element (e.g. curl -XPOST localhost:29200/*/_close), the variable didn't get replaced with the current '*' value, but with the empty string, which leads to an error as empty index is not allowed by open/close index. Closes #4564
2013-12-24 09:29:59 -05:00
- do:
indices.create:
index: test_index3
[TEST] indices.open REST tests need 0 replicas With replicas the search requests might go to shards that are not ready, since we have a wait for yellow. We can now switch to wait for green as well.
2014-05-22 04:55:57 -04:00
body:
settings:
number_of_replicas: 0
Fixed open/close index api when using wildcard only Named wildcards were not always properly replaced with proper values by PathTrie. Delete index (curl -XDELETE localhost:9200/*) worked anyway as the named wildcard is the last path element (and even if {index} didn't get replaced with '*', the empty string would have mapped to all indices anyway). When the named wildcard wasn't the last path element (e.g. curl -XPOST localhost:29200/*/_close), the variable didn't get replaced with the current '*' value, but with the empty string, which leads to an error as empty index is not allowed by open/close index. Closes #4564
2013-12-24 09:29:59 -05:00
- do:
cluster.health:
[TEST] indices.open REST tests need 0 replicas With replicas the search requests might go to shards that are not ready, since we have a wait for yellow. We can now switch to wait for green as well.
2014-05-22 04:55:57 -04:00
wait_for_status: green
Fixed open/close index api when using wildcard only Named wildcards were not always properly replaced with proper values by PathTrie. Delete index (curl -XDELETE localhost:9200/*) worked anyway as the named wildcard is the last path element (and even if {index} didn't get replaced with '*', the empty string would have mapped to all indices anyway). When the named wildcard wasn't the last path element (e.g. curl -XPOST localhost:29200/*/_close), the variable didn't get replaced with the current '*' value, but with the empty string, which leads to an error as empty index is not allowed by open/close index. Closes #4564
2013-12-24 09:29:59 -05:00
---
"All indices":
- do:
indices.close:
index: _all
- do:
catch: forbidden
search:
index: test_index2
- do:
indices.open:
index: _all
- do:
cluster.health:
[TEST] indices.open REST tests need 0 replicas With replicas the search requests might go to shards that are not ready, since we have a wait for yellow. We can now switch to wait for green as well.
2014-05-22 04:55:57 -04:00
wait_for_status: green
Fixed open/close index api when using wildcard only Named wildcards were not always properly replaced with proper values by PathTrie. Delete index (curl -XDELETE localhost:9200/*) worked anyway as the named wildcard is the last path element (and even if {index} didn't get replaced with '*', the empty string would have mapped to all indices anyway). When the named wildcard wasn't the last path element (e.g. curl -XPOST localhost:29200/*/_close), the variable didn't get replaced with the current '*' value, but with the empty string, which leads to an error as empty index is not allowed by open/close index. Closes #4564
2013-12-24 09:29:59 -05:00
- do:
search:
index: test_index2
---
"Trailing wildcard":
- do:
indices.close:
index: test_*
- do:
catch: forbidden
search:
index: test_index2
- do:
indices.open:
index: test_*
- do:
cluster.health:
[TEST] indices.open REST tests need 0 replicas With replicas the search requests might go to shards that are not ready, since we have a wait for yellow. We can now switch to wait for green as well.
2014-05-22 04:55:57 -04:00
wait_for_status: green
Fixed open/close index api when using wildcard only Named wildcards were not always properly replaced with proper values by PathTrie. Delete index (curl -XDELETE localhost:9200/*) worked anyway as the named wildcard is the last path element (and even if {index} didn't get replaced with '*', the empty string would have mapped to all indices anyway). When the named wildcard wasn't the last path element (e.g. curl -XPOST localhost:29200/*/_close), the variable didn't get replaced with the current '*' value, but with the empty string, which leads to an error as empty index is not allowed by open/close index. Closes #4564
2013-12-24 09:29:59 -05:00
- do:
search:
index: test_index2
---
"Only wildcard":
- do:
indices.close:
index: '*'
- do:
catch: forbidden
search:
index: test_index3
- do:
indices.open:
index: '*'
- do:
cluster.health:
[TEST] indices.open REST tests need 0 replicas With replicas the search requests might go to shards that are not ready, since we have a wait for yellow. We can now switch to wait for green as well.
2014-05-22 04:55:57 -04:00
wait_for_status: green
Fixed open/close index api when using wildcard only Named wildcards were not always properly replaced with proper values by PathTrie. Delete index (curl -XDELETE localhost:9200/*) worked anyway as the named wildcard is the last path element (and even if {index} didn't get replaced with '*', the empty string would have mapped to all indices anyway). When the named wildcard wasn't the last path element (e.g. curl -XPOST localhost:29200/*/_close), the variable didn't get replaced with the current '*' value, but with the empty string, which leads to an error as empty index is not allowed by open/close index. Closes #4564
2013-12-24 09:29:59 -05:00
- do:
search:
Fix YAML in test/indices.open/20_multiple_indices.yaml
2014-01-13 07:17:30 -05:00
index: test_index3