# Cross-indexd fitering using Kibana in v5.6.1
**URL:** https://discuss.elastic.co/t/cross-indexd-fitering-using-kibana-in-v5-6-1/134573
**Category:** Kibana
**Created:** [June 5, 2018, 9:05am UTC](https://discuss.elastic.co/t/cross-indexd-fitering-using-kibana-in-v5-6-1/134573 "2018-06-05T09:05:29Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@alonguterman1](https://discuss.elastic.co/u/alonguterman1)
#### Post date: [June 5, 2018, 9:05am UTC](https://discuss.elastic.co/t/cross-indexd-fitering-using-kibana-in-v5-6-1/134573/1 "2018-06-05T09:05:30Z")
Hi,
Currently we have our data saved in elasticsearch version 5.6.1, by using one index with several types in it, and with parent-child reltaions.
This approach allows us in Kibana to make queries and filters easily in a single dashboard, since all the data is in one index.
This will not be supported in next versions of elastic 😑.
To my understanding from other posts, if we are to re-arrange our data in elastic, in a way that each type is an index - we will lose the ability to keep using the Kibana the way we currently use it (by applying a filter to the parent we change the output of all its children).
One option would be to create an index for each child-type, do not use the parent-child paradigm, and each document would have additional properties that were in the parent before this change, so we could make the same queries.
Is that a good approach when thinking big-data wise?
Thanks,
---
### Author:  [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)
#### Post date: [June 5, 2018, 6:15pm UTC](https://discuss.elastic.co/t/cross-indexd-fitering-using-kibana-in-v5-6-1/134573/2 "2018-06-05T18:15:26Z")
Hey @alonguterman1, great question!
When it comes to migrating away from multiple types in the same index, there are a few alternatives (borrowed from [this](https://www.elastic.co/blog/kibana-6-removal-of-mapping-types) blogpost)
> Using a single index per type
> Collapsing all properties under a single type
> Creating a custom type field, and nesting all types under a single type.
Since you are currently using a parent/child relationship currently, you won't want to use the "single index per type" option, but that still leaves us with the latter 2 solutions, either of which should work with the new
[join datatype](https://www.elastic.co/guide/en/elasticsearch/reference/6.0/parent-join.html) that is essentially a typeless parent/child.
---
### Author:  [@alonguterman1](https://discuss.elastic.co/u/alonguterman1)
#### Post date: [June 10, 2018, 10:48am UTC](https://discuss.elastic.co/t/cross-indexd-fitering-using-kibana-in-v5-6-1/134573/3 "2018-06-10T10:48:51Z")
Thanks 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 8, 2018, 10:48am UTC](https://discuss.elastic.co/t/cross-indexd-fitering-using-kibana-in-v5-6-1/134573/4 "2018-07-08T10:48:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.