# New Structure for 6.0

**URL:** <https://discuss.elastic.co/t/new-structure-for-6-0/110373>\
**Category:** Elasticsearch\
**Created:** [December 5, 2017, 2:24pm UTC](https://discuss.elastic.co/t/new-structure-for-6-0/110373 "2017-12-05T14:24:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DedMorozzz.kh](https://avatars.discourse-cdn.com/v4/letter/d/e56c9b/32.png) [@DedMorozzz.kh](https://discuss.elastic.co/u/DedMorozzz.kh)\
**Post date:** [December 5, 2017, 2:24pm UTC](https://discuss.elastic.co/t/new-structure-for-6-0/110373/1 "2017-12-05T14:24:37Z")

</div>

Hi all, I already have structure for 2.4 version. I want migrate on 6.0, and read about breaking changes about types.  
So, current structure is next: I have main type - publisher. And 3 "sub-types": accounts, audience and interests  
Publisher is parent  
Accounts, Audience, Interests are children

In 6.0 types was removed, and I read about single indexes and nested items  
So question about nested items: what about performance, where i save all data in one index with 3 nested items (in 2.4 i use inner\_hits only for needed types)?

And question 2 with different indexes:  
is real use index publisher AND accounts AND .... But select from accounts only data where publisherId exists from first request part. Example with SQL:

SELECT \* FROM publisher\_index P  
JOIN account\_index A ON A.PublisherId = [P.Id](http://P.Id)  
WHERE P.Name='test' AND A.TotalSubscribers \> 2500

Is it real?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 2, 2018, 2:24pm UTC](https://discuss.elastic.co/t/new-structure-for-6-0/110373/2 "2018-01-02T14:24:46Z")

</div>

Closed on January 2, 2018, 2:24pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.