Hi Davide,
I think 'OR' gets passed as constraints to underlying index engine
(property, lucene, solr) etc. For lucene case (I guess solr too), I
think having a bunch is of 'OR' is more useful than doing a union at
query engine as:
* single query to lucene would save multiple hops into index
*
On 03/02/2016 11:28, Vikas Saurabh wrote:
> Hi Davide,
>
> I think 'OR' gets passed as constraints to underlying index engine
> (property, lucene, solr) etc. For lucene case (I guess solr too), I
> think having a bunch is of 'OR' is more useful than doing a union at
> query engine as:
> * single
Hello team,
back in 1.3.9 we introduced
https://issues.apache.org/jira/browse/OAK-1617 which indirectly
addressed https://issues.apache.org/jira/browse/OAK-2660 and
https://issues.apache.org/jira/browse/OAK-2539.
This has been proven to work out fine. However if we come from an xpath
query which
