Hey Jettro, Indeed with shield the behaviour of the cluster when it comes to wildcards is a bit different. While with vanilla elasticsearch, we expand wildcards based on the index options, with shield we take the security context into account and only expand to those indices the user has privileges on. see:
http://www.elasticsearch.org/guide/en/shield/current/limitations.html#_changes_in_index_wildcard_behavior and http://www.elasticsearch.org/guide/en/shield/current/securing-aliases.html On Thursday, March 5, 2015 at 12:41:50 PM UTC+1, Jettro Coenradie wrote: > > Hi I am running the following code to remove indexes, if there is no index > with the specified pattern, a shield enabled cluster throws an exception. > To my opinion I have marked the options in a way that this should not > happen. If I use the same code on a cluster without shield enabled, > everything works fine. > > client.admin().indices().prepareDelete(this.index + "*") > .setIndicesOptions(IndicesOptions.fromOptions(true, true, > true, false)).get(); > > > Is this an issue with Shield? The user I provide has admin rights. > > thanks > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5b7a659a-0e71-40ee-a4d9-7e2ef1c59b9a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
