[OAK-10532] Cost estimation for "not(@x)" calculates cost for "@x='value'" instead

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.70.0
• Component/s: lucene
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 03/Nov/23 15:38
• Updated: 01/Oct/24 04:24
• Resolved: 04/Sep/24 17:24

Description

The cost estimation for a query that uses a Lucene index calculates the cost incorrectly if there is a "not(<property>)" condition. Examples:

/jcr:root//*[(not(@x)) and (not(@y))

The Lucene query is then:

+:nullProps:x +:nullProps:y

But the cost estimation seems to take into account the number of documents for the fields "x" and "y", instead of the field ":nullProps"

Issue Links

• duplicates: OAK-10648 "IS NULL" (Null Props) Cause Incorrect Query Estimation
• links to: GitHub Pull Request #1673