[
https://issues.apache.org/jira/browse/OAK-10532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877457#comment-17877457
]
Thomas Mueller commented on OAK-10532:
--------------------------------------
https://github.com/apache/jackrabbit-oak/pull/1673/files
> 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
> Assignee: Thomas Mueller
> Priority: Major
>
> 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)
