I think the experimental flag can be removed from the documentation page.
It has been out in the wild for quite some time now. We keep on improving
the has_parent and the parent/child support in general. For example
recently in 0.90.1 we reduced the memory footprint of parent/child
significantly.
Besides the memory considerations, I would also recommend the use the
warmer api in combinations with parent/child. The allows the loading of the
id_cache to happen in a controlled manner as part of the refresh. If you
don't use warmers then all the initial first searches try the load the
values for the id_cache, but only one search request wins, so a lot
of unnecessary work is done as part of the first searches.
If you're planning on using parent/child on a index with a lot of documents
(like 100M docs), you might need to increase the number of primary shards
and have sufficient nodes for those shards in order to make searches the
parent/child queries execute within an acceptable time range.
On 25 June 2013 21:22, George Stathis gstathis@gmail.com wrote:
Hi folks, I see in the docs that the has_parenthttp://www.elasticsearch.org/guide/reference/query-dsl/has-parent-query/query is noted as experimental since 0.19.10 . Other than the memory
considerations, are there any other gotchas that we should be aware of?Thank you in advance.
--
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.
--
Met vriendelijke groet,
Martijn van Groningen
--
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.