I have 3 level hierarchy which I want to model as parent/child.
The documentation says that the grand-child should be indexed with parentas 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.
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 email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3c30da44-008b-4d0c-b45b-d50fca48d95c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.