<p dir="auto">When specifying one index only, it makes sense to throw this. When querying on multiple indexes, this should be thrown only if none of the indexes were found. Details on non-existing indices can be embedded in the response, letting the consumer decide if this result is desired or not.</p>
<p dir="auto">At least have the option of having this configurable.</p>
<p dir="auto">This is very important to have for scenarios like the "log file indexing" scenario <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/kimchy/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/kimchy">@kimchy</a> talks about</p>
<p dir="auto">For applications using daily indexes it would be useful if elasticsearch didn't return an error if at least one of the specified indexes existed.  Currently before each query I need to check what indexes exist incase a daily index was removed outside my application .   If the current behavior is required, then maybe add a flag for new behavior?</p>
<p dir="auto">Reproduce:<br>
curl <a href="http://localhost:9200/sessions-120813/session/1" rel="nofollow">http://localhost:9200/sessions-120813/session/1</a> -d '{"test": 1}'<br>
curl '<a href="http://localhost:9200/sessions-120812,sessions-120813/session/_search?query=test:1" rel="nofollow">http://localhost:9200/sessions-120812,sessions-120813/session/_search?query=test:1</a>'<br>
{"error":"IndexMissingException[[sessions-120812] missing]","status":404}</p>
<p dir="auto">Desired response:<br>
{"took":2,"timed_out":false,"_shards":{"total":5,"successful":5,"failed":0},"hits":{"total":1,"max_score":1.0,"hits":[{"_index":"sessions-120813","_type":"session","_id":"1","_score":1.0, "_source" : {"test": 1}}]}}</p>