Thomas Mueller created OAK-12007:
------------------------------------
Summary: XPath with "or" conditions should not always be converted
to "union"
Key: OAK-12007
URL: https://issues.apache.org/jira/browse/OAK-12007
Project: Jackrabbit Oak
Issue Type: Improvement
Components: query
Reporter: Thomas Mueller
In OAK-1432, XPath queries with "or" conditions are always converted to "union"
queries.
There are some queries that do not benefit from this forced conversion to
"union", for example queries that use elasticsearch indexes for both parts, but
where one of the properties is not indexed. In general, it would be better to
compare the cost of the union with the cost of the non-union query, and then
pick the one with the lower cost.
In fact, for SQL-2 queries with "or" conditions, that is how it's working since
OAK-1617.
It's a bit dangerous now (after such a long time) to always disable the forced
"union" conversion for XPath queries. But, what we could do is disable the
forced conversion using a feature toggle.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
