Even in a simple parent/child relationship, if a child has many parents,
how does ES ensure that when a new parent is indexed, both the new parent
and existing child (and all its parents) get routed to the same shard?
Even in a simple parent/child relationship, if a child has many parents,
how does ES ensure that when a new parent is indexed, both the new parent
and existing child (and all its parents) get routed to the same shard?
Version 0.18.7 has parent child support, but this version doesn't
support the has_parent filter/query all other child like
filters/queries are supported. The latest 0.19 and 0.20 versions have
a more efficient parent/child implementation.
As is described in the referred email, you will need to use the top
parent id as routing value for its sub parents and children documents
during indexing. As Lukas wrote, a child document can only point to
one parent document. That parent can point to a grand parent.
Parent and child document relation can only be established in the
same index. The relation is established between types in the same
index. Each document type (parent, child) has its own mapping
describing the relation with the _parent mapping.
Even in a simple parent/child relationship, if a child has many parents,
how does ES ensure that when a new parent is indexed, both the new parent
and existing child (and all its parents) get routed to the same shard?
Version 0.18.7 has parent child support, but this version doesn't
support the has_parent filter/query all other child like
filters/queries are supported. The latest 0.19 and 0.20 versions have
a more efficient parent/child implementation.
As is described in the referred email, you will need to use the top
parent id as routing value for its sub parents and children documents
during indexing. As Lukas wrote, a child document can only point to
one parent document. That parent can point to a grand parent.
Parent and child document relation can only be established in the
same index. The relation is established between types in the same
index. Each document type (parent, child) has its own mapping
describing the relation with the _parent mapping.
Even in a simple parent/child relationship, if a child has many parents,
how does ES ensure that when a new parent is indexed, both the new
parent
and existing child (and all its parents) get routed to the same shard?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.