Kevin Risden created LUCENE-10534:
-------------------------------------
Summary: MinFloatFunction / MaxFloatFunction exists check is slow
Key: LUCENE-10534
URL: https://issues.apache.org/jira/browse/LUCENE-10534
Project: Lucene - Core
Issue Type: Improvement
Reporter: Kevin Risden
Assignee: Kevin Risden
MinFloatFunction
(https://github.com/apache/lucene/blob/main/lucene/queries/src/java/org/apache/lucene/queries/function/valuesource/MinFloatFunction.java)
and MaxFloatFunction
(https://github.com/apache/lucene/blob/main/lucene/queries/src/java/org/apache/lucene/queries/function/valuesource/MaxFloatFunction.java)
both check if values exist. This is needed since the underlying valuesource
returns 0.0f as either a valid value or as a value when the document doesn't
have a value.
Even though this is changed to anyExists and short circuits in the case a value
is found in any document, the worst case is that there is no value found and
requires checking all the way through to the raw data. This is only needed when
0.0f is returned and need to determine if it is a valid value or the not found
case.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
