I do not fully understand your challenge and the role you want ES to play.
If you operate with IDs, you can iterate through the multiget response and
visit contributors, accessors etc. and select a unique list of members in
your app simply by looking at the doc ID.
It is not very elegant to assign more than one ID to the same entity,
because then an ID is no longer unique. Then you'd have to address the
problem of entity identification or entity matching to obtain unique IDs,
which is outside the scope of ES, it is in the domain of the app.
Parent/child is for special queries on parent/child relationships
(has_parent/has_children) and updating parents and children docs on their
own steps, where children docs can link to a unique parent ID. So I'm not
sure why parent/child can solve your challenge.
For more inspiration about relationships, I recommend this overview of
Zachary Tong
Jörg
--
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.
For more options, visit https://groups.google.com/groups/opt_out.