# Wildcard indices patterns on closed indices gives IndexClosedException **URL:** \ **Category:** Elasticsearch\ **Created:** [May 22, 2015, 2:39pm UTC](https://discuss.elastic.co/t/wildcard-indices-patterns-on-closed-indices-gives-indexclosedexception/23671 "2015-05-22T14:39:17Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![John\_Bush\_3](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@John\_Bush\_3](https://discuss.elastic.co/u/John_Bush_3)\ **Post date:** [May 22, 2015, 2:39pm UTC](https://discuss.elastic.co/t/wildcard-indices-patterns-on-closed-indices-gives-indexclosedexception/23671/1 "2015-05-22T14:39:17Z")
If I do a search like this and that index pattern has a closed index: [http://custer.s03.filex.com/fps-invs\_672dd3cb-f529-4aaa-b10c-8b5076591eb3\*/\_search](http://custer.s03.filex.com/fps-invs_672dd3cb-f529-4aaa-b10c-8b5076591eb3*/_search) I get this: IndexClosedException[[fps-invs\_672dd3cb-f529-4aaa-b10c-8b5076591eb3\_2014-12] closed] shouldn't a search ignore closed indices ? This seems like a bug, is there some workaround to this, that does involved moving/deleting the closed indices ? using 1.4.4 -- CONFIDENTIALITY NOTICE: The preceding and/or attached information may be confidential or privileged. It should be used or disseminated solely for the purpose of conducting business with Trax. If you are not an intended recipient, please notify the sender by replying to this message and then delete the information from your system. Thank you for your cooperation. ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/4358745a-fae1-44ce-8bd5-06bb9141b736%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4358745a-fae1-44ce-8bd5-06bb9141b736%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![John\_Bush\_3](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@John\_Bush\_3](https://discuss.elastic.co/u/John_Bush_3)\ **Post date:** [May 22, 2015, 2:55pm UTC](https://discuss.elastic.co/t/wildcard-indices-patterns-on-closed-indices-gives-indexclosedexception/23671/2 "2015-05-22T14:55:33Z")
Nevermind it was actually an alias causing the issue. On Fri, May 22, 2015 at 7:39 AM, John Bush [john.bush@traxtech.com](mailto:john.bush@traxtech.com) wrote: > If I do a search like this and that index pattern has a closed index: > > [http://custer.s03.filex.com/fps-invs\_672dd3cb-f529-4aaa-b10c-8b5076591eb3\*/\_search](http://custer.s03.filex.com/fps-invs_672dd3cb-f529-4aaa-b10c-8b5076591eb3*/_search) > > I get this: > > IndexClosedException[[fps-invs\_672dd3cb-f529-4aaa-b10c-8b5076591eb3\_2014-12] > closed] > > shouldn't a search ignore closed indices ? This seems like a bug, is there > some workaround to this, that does involved moving/deleting the closed > indices ? > > using 1.4.4 > > CONFIDENTIALITY NOTICE: The preceding and/or attached information may be > confidential or privileged. It should be used or disseminated solely for the > purpose of conducting business with Trax. If you are not an intended > recipient, please notify the sender by replying to this message and then > delete the information from your system. Thank you for your cooperation. > > ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) > > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/M3lpBKvEV20/unsubscribe](https://groups.google.com/d/topic/elasticsearch/M3lpBKvEV20/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/4358745a-fae1-44ce-8bd5-06bb9141b736%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4358745a-fae1-44ce-8bd5-06bb9141b736%40googlegroups.com). > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- John Bush Vice President Platform services Trax Technologies, Inc. M: 480-227-2910 > **[Trax Technologies | Global Freight Audit & Spend Management](https://www.traxtech.com/)** > > Discover how global companies leverage Trax’s solutions for a strategic advantage. AI-powered spend management optimizes costs, enhances visibility, and mitigates risks. -- CONFIDENTIALITY NOTICE: The preceding and/or attached information may be confidential or privileged. It should be used or disseminated solely for the purpose of conducting business with Trax. If you are not an intended recipient, please notify the sender by replying to this message and then delete the information from your system. Thank you for your cooperation. ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CABnnkhuM3ap-%3D%2B0JuoiCjBGNpe-P4DbG5ZKANMzEGY3ir%3DTkLw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CABnnkhuM3ap-%3D%2B0JuoiCjBGNpe-P4DbG5ZKANMzEGY3ir%3DTkLw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:12am UTC](https://discuss.elastic.co/t/wildcard-indices-patterns-on-closed-indices-gives-indexclosedexception/23671/3 "2017-07-06T00:12:19Z")