Parent/Child Self Referencing documents

Hello:

We are going to start indexing transaction/activity information and these
can be nested within each other (like a stack frame). So activity A is the
parent of activity B & C etc. Is there any support (or plans) to handle
this type of parent/child relationship? Any suggestions on how to approach
mapping these events? The main type of query that would take advantage of
this structure would be something like "given a root activity id, display
the tree of activities stemming off of it"

Thanks!
Andy Ochsner

--
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.

Play around with the nested type:

I think it will work for you. There are also some parent/child document
relationships. Some easier to follow details on both these are here:

Best Regards,
Paul

On Wednesday, February 27, 2013 9:04:33 AM UTC-7, Andrew Ochsner wrote:

Hello:

We are going to start indexing transaction/activity information and these
can be nested within each other (like a stack frame). So activity A is the
parent of activity B & C etc. Is there any support (or plans) to handle
this type of parent/child relationship? Any suggestions on how to approach
mapping these events? The main type of query that would take advantage of
this structure would be something like "given a root activity id, display
the tree of activities stemming off of it"

Thanks!
Andy Ochsner

--
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.