# Modelling data with Joins in Elasticsearch

**URL:** <https://discuss.elastic.co/t/modelling-data-with-joins-in-elasticsearch/108378>\
**Category:** Elasticsearch\
**Created:** [November 20, 2017, 12:01pm UTC](https://discuss.elastic.co/t/modelling-data-with-joins-in-elasticsearch/108378 "2017-11-20T12:01:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kartik\_jain](https://avatars.discourse-cdn.com/v4/letter/k/48db29/32.png) [@kartik\_jain](https://discuss.elastic.co/u/kartik_jain)\
**Post date:** [November 20, 2017, 12:01pm UTC](https://discuss.elastic.co/t/modelling-data-with-joins-in-elasticsearch/108378/1 "2017-11-20T12:01:30Z")

</div>

I indent to transfer data from a RDBMS source to elasticsearch and perform various aggregation queries on it. For this purpose, I need to perform some joins on the data. I was looking into parent-child relationships.  
I need suggestions on how to model and index the data to perform aggregation queries

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 20, 2017, 12:25pm UTC](https://discuss.elastic.co/t/modelling-data-with-joins-in-elasticsearch/108378/2 "2017-11-20T12:25:19Z")

</div>

It is always better to do joins at index time instead of using parent child IMO.

May share some typical data you have?

---

<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:** [December 18, 2017, 12:25pm UTC](https://discuss.elastic.co/t/modelling-data-with-joins-in-elasticsearch/108378/3 "2017-12-18T12:25:29Z")

</div>

Closed on December 18, 2017, 12:25pm UTC

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