# Parent/child routing **URL:** \ **Category:** Elasticsearch\ **Created:** [May 11, 2014, 9:21am UTC](https://discuss.elastic.co/t/parent-child-routing/17446 "2014-05-11T09:21:55Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![shrinidhi\_chaudhari](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@shrinidhi\_chaudhari](https://discuss.elastic.co/u/shrinidhi_chaudhari)\ **Post date:** [May 11, 2014, 9:21am UTC](https://discuss.elastic.co/t/parent-child-routing/17446/1 "2014-05-11T09:21:55Z")
Hello folks, I have 3 level hierarchy which I want to model as parent/child. The documentation says that the grand-child should be indexed with _parent_as well as _routing_ values so they end up in the same shard. Is there a way to circumvent this requirement, because I do not want to lookup the grand parents ID while inserting a grand-child? Else, is there a way where I can specify that the routing value is the parents routing value. Thanks you. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/3c30da44-008b-4d0c-b45b-d50fca48d95c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3c30da44-008b-4d0c-b45b-d50fca48d95c%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:30am UTC](https://discuss.elastic.co/t/parent-child-routing/17446/2 "2017-07-06T01:30:19Z")