Thomas Mueller created OAK-10532:
------------------------------------
Summary: Cost estimation for "not(@x)" calculates cost for
"@x='value'" instead
Key: OAK-10532
URL: https://issues.apache.org/jira/browse/OAK-10532
Project: Jackrabbit Oak
Issue Type: Improvement
Components: lucene
Reporter: Thomas Mueller
The cost estimation for a query that uses a Lucene index calculates the cost
incorrectly if there is a "not(<property>)" condition. Examples:
{noformat}
/jcr:root//*[(not(@x)) and (not(@y))
{noformat}
The Lucene query is then:
{noformat}
+:nullProps:x +:nullProps:y
{noformat}
But the cost estimation seems to take into account the number of documents for
the fields "x" and "y", instead of the field ":nullProps"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
