From 389b2be08a0df1463c45bec6c481839cfed3d8d2 Mon Sep 17 00:00:00 2001 From: javanna Date: Thu, 14 Jan 2016 17:19:20 +0100 Subject: [PATCH] [TEST] blacklist get aliases test against closed indices Shield expands wildcards to concrete names (aliases or indices) before each request gets executed in es core. It never resolves aliases to concrete indices though, as permissions may be set against aliases rather than indices. During this resolution, it also looks at the state of the indices and the current indices options (expand_wildcards) to expand only to indices with the relevant state. When it comes to aliases though, they may point to multiple indices each one having a different state, so it always expands ignoring expand_wildcards. At that point the request will contain the explicit name of the alias, no wildcards, thus the expand_wildcards option will have no effect in core. ignore_unavailable could be used instead when interacting with shield, which would affect how aliases are resolved to multiple indices. In this case we can only blacklist the test in shield, as it will return both the closed index and the open one. Original commit: elastic/x-pack-elasticsearch@54c11dfc318fa59c541485789ce9714c298abd5e --- elasticsearch/qa/shield-core-rest-tests/build.gradle | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/elasticsearch/qa/shield-core-rest-tests/build.gradle b/elasticsearch/qa/shield-core-rest-tests/build.gradle index ef5d461a0a4..d907108e267 100644 --- a/elasticsearch/qa/shield-core-rest-tests/build.gradle +++ b/elasticsearch/qa/shield-core-rest-tests/build.gradle @@ -27,7 +27,8 @@ integTest { 'indices.recovery/10_basic/Indices recovery test*', 'indices.shard_stores/10_basic/no indices test', 'cat.nodeattrs/10_basic/Test cat nodes attrs output', - 'bulk/40_fields/Fields'].join(',') + 'bulk/40_fields/Fields', + 'indices.get_alias/10_basic/Get alias against closed indices'].join(',') cluster { plugin 'x-pack', project(':x-plugins:elasticsearch:x-pack')