# ES6.0: multiple types, indexes, relationships puzzle

**URL:** https://discuss.elastic.co/t/es6-0-multiple-types-indexes-relationships-puzzle/108984
**Category:** Elasticsearch
**Created:** [November 24, 2017, 7:32am UTC](https://discuss.elastic.co/t/es6-0-multiple-types-indexes-relationships-puzzle/108984 "2017-11-24T07:32:47Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![iti](https://avatars.discourse-cdn.com/v4/letter/i/b19c9b/32.png) [@iti](https://discuss.elastic.co/u/iti)
#### Post date: [November 28, 2017, 7:29pm UTC](https://discuss.elastic.co/t/es6-0-multiple-types-indexes-relationships-puzzle/108984/4 "2017-11-28T19:29:25Z")

</div>

I have basically asked the same question, but no one has given any answer yet.

> [@ES 6.0 1 type 1 index issues](https://discuss.elastic.co/t/es-6-0-1-type-1-index-issues/109291):
>
> Currently, my ES(5.6.3) mapping is like this: Index: Parent Type, Child Type 1, Child Type 2, ........ Child Type 70 Each Child Type has its own nested documents. Parent Type and Child Type have a common Key (ID). So, using has has\_child or has\_parent is very convenient. With 1 type 1 index, they are 2 ways to convert it: 1. create total of 71 indexes with 1 type. 2. create a custom "type" field and lump all fields in each parent/child type i…

My situation is a lot more complex. ES did not provide any easy way to convert multiple type with parent child relationship in 6.0.

ES should have keep the existing way of handling parent child relationship and hide the detail internal stuff from the user.

Even if they provide the conversion method, I have to redo most of my project. No enterprise software would dare to do this kind of drastic change that requires the customer to redo almost all the work.

---

_[View the full topic](https://discuss.elastic.co/t/es6-0-multiple-types-indexes-relationships-puzzle/108984)._