# Search perfomance using many indices with one alias

**URL:** <https://discuss.elastic.co/t/search-perfomance-using-many-indices-with-one-alias/115665>\
**Category:** Elasticsearch\
**Created:** [January 16, 2018, 8:36am UTC](https://discuss.elastic.co/t/search-perfomance-using-many-indices-with-one-alias/115665 "2018-01-16T08:36:44Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Jul](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@Jul](https://discuss.elastic.co/u/Jul)\
**Post date:** [January 18, 2018, 8:55am UTC](https://discuss.elastic.co/t/search-perfomance-using-many-indices-with-one-alias/115665/7 "2018-01-18T08:55:41Z")

</div>

Hey code\_blue,

thanks for your hints. Especially the one about schema less model helps a lot to understand how the queries are performed.

A term query with type1.field1 does not yield any results:

```
{
  "query": {
    "query_string": {
      "default_field": "type1.field1",
      "query": "test"
    }
  }
}

```

I found a very well perfoming solution using IndicesQuery, but it is deprecated. I opened a new topic for my question as it might be relevant to other users as well: [Search performance: IndicesQuery (deprecated) vs. query on field \_index](https://discuss.elastic.co/t/search-performance-indicesquery-deprecated-vs-query-on-field-index/115999)

Jul

---

_[View the full topic](https://discuss.elastic.co/t/search-perfomance-using-many-indices-with-one-alias/115665)._