# What is the status of one type per index in ElasticSearch 6.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [June 22, 2017, 9:01am UTC](https://discuss.elastic.co/t/what-is-the-status-of-one-type-per-index-in-elasticsearch-6-0/90414 "2017-06-22T09:01:45Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![frank-montyne](https://avatars.discourse-cdn.com/v4/letter/f/41988e/32.png) [@frank-montyne](https://discuss.elastic.co/u/frank-montyne)\ **Post date:** [June 22, 2017, 9:01am UTC](https://discuss.elastic.co/t/what-is-the-status-of-one-type-per-index-in-elasticsearch-6-0/90414/1 "2017-06-22T09:01:45Z")
We recently have had a thread discussing the fact that in ElasticSearch 6.0 multiple types per index would not be allowed anymore. The thread was closed but without a real answer whether this will effectively be implemented or not. Since this impacts so many users I think we have the right to know upfront if this has been firmly decided. I'm sure this would cause major headaches and force major rewrites of existing software. I still hope this "feature" will not see the light of day. In case it does I have one request: make it invisible for the developer. This could be done by not letting the developer work with physical indices directly anymore but a sort of virtual compound index (= a combination of indices each containing one type) and let Elasticsearch do the heavy lifting of accessing the correct physical index to store and retrieve data. That way nothing changes for a developer perspective but underlyingly a single index per type is used. Maybe this is the best of both worlds? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 22, 2017, 9:08am UTC](https://discuss.elastic.co/t/what-is-the-status-of-one-type-per-index-in-elasticsearch-6-0/90414/2 "2017-06-22T09:08:18Z")
Yes, it has been firmly decided. ---
**Author:** ![frank-montyne](https://avatars.discourse-cdn.com/v4/letter/f/41988e/32.png) [@frank-montyne](https://discuss.elastic.co/u/frank-montyne)\ **Post date:** [June 22, 2017, 9:19am UTC](https://discuss.elastic.co/t/what-is-the-status-of-one-type-per-index-in-elasticsearch-6-0/90414/3 "2017-06-22T09:19:49Z")
What do you think of my suggestion to make it invisible to the developer? ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [June 22, 2017, 9:24am UTC](https://discuss.elastic.co/t/what-is-the-status-of-one-type-per-index-in-elasticsearch-6-0/90414/4 "2017-06-22T09:24:48Z")
The concept of physical indices and virtual compound indices are already implemented by index aliases mechanism. Not sure why there must a "major rewrite"? All fields in an index must already be non-conflicting, no matter how many mappings are used. For example, from the early days of Elasticsearch I was convinced by the "Book/CD" example, that field mappings must be non-conflicting and additive, for index types should be useful for "search views" on an index. This kind of separation is already controlled by my application, e.g. by a search filter. Search filters are more dynamic than an index type. So I decided to implement custom search filter fields, and ignored the index type mechanism. ---
**Author:** ![frank-montyne](https://avatars.discourse-cdn.com/v4/letter/f/41988e/32.png) [@frank-montyne](https://discuss.elastic.co/u/frank-montyne)\ **Post date:** [June 22, 2017, 9:30am UTC](https://discuss.elastic.co/t/what-is-the-status-of-one-type-per-index-in-elasticsearch-6-0/90414/5 "2017-06-22T09:30:17Z")
Index aliases containing multiple indices cannot be used for storing/updating/deleting data. ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [June 22, 2017, 12:40pm UTC](https://discuss.elastic.co/t/what-is-the-status-of-one-type-per-index-in-elasticsearch-6-0/90414/6 "2017-06-22T12:40:32Z")
Sure, as I said, index aliases are for search filtering. For indexing, you can try to append index name with the index type name and use that combination as the index name. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 20, 2017, 12:40pm UTC](https://discuss.elastic.co/t/what-is-the-status-of-one-type-per-index-in-elasticsearch-6-0/90414/7 "2017-07-20T12:40:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.