# Porting a relational structure to Elasticsearch - Nested or Parent/Child

**URL:** <https://discuss.elastic.co/t/porting-a-relational-structure-to-elasticsearch-nested-or-parent-child/32920>\
**Category:** Elasticsearch\
**Created:** [October 24, 2015, 8:50pm UTC](https://discuss.elastic.co/t/porting-a-relational-structure-to-elasticsearch-nested-or-parent-child/32920 "2015-10-24T20:50:27Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![bgow](https://avatars.discourse-cdn.com/v4/letter/b/7993a0/32.png) [@bgow](https://discuss.elastic.co/u/bgow)\
**Post date:** [November 20, 2015, 8:42pm UTC](https://discuss.elastic.co/t/porting-a-relational-structure-to-elasticsearch-nested-or-parent-child/32920/10 "2015-11-20T20:42:09Z")

</div>

I stuck with using a nested structure and posted additional details about getting my data properly formatted and imported in these threads ([1](https://discuss.elastic.co/t/logstash-mutate-filter-rename-exception-in-filterworker-exception-indexerror-string-not-matched/33438/3), [2](https://stackoverflow.com/questions/33662850/formatting-postgres-json-output-for-nested-elasticsearch-structure), [3](https://stackoverflow.com/questions/33535186/can-jq-perform-aggregation-across-files/33835625#33835625)).

---

_[View the full topic](https://discuss.elastic.co/t/porting-a-relational-structure-to-elasticsearch-nested-or-parent-child/32920)._