Is there any logical reason againt using nested hasChildQuery queries?
Searching for both individually works fine returning each time the
correct parents. I assumed that combining the two would result in the
most upper parent returned as result.
Is there any logical reason againt using nested hasChildQuery queries?
Searching for both individually works fine returning each time the
correct parents. I assumed that combining the two would result in the
most upper parent returned as result.
Is there any logical reason againt using nested hasChildQuery queries?
Searching for both individually works fine returning each time the
correct parents. I assumed that combining the two would result in the
most upper parent returned as result.
Is there any logical reason againt using nested hasChildQuery queries?
Searching for both individually works fine returning each time the
correct parents. I assumed that combining the two would result in the
most upper parent returned as result.
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.