timgrein opened a new pull request, #13383: URL: https://github.com/apache/lucene/pull/13383
Related to https://github.com/apache/lucene/issues/13375 ### Description With this change `ValueSourceQuery` and `MultiValueSourceQuery` will be rewritten to a `FieldExistsQuery`, if the query range uses the maximum range possible (`[Long.MIN_VALUE, Long.MAX_VALUE]`) as the exact values of the queried field won't matter anymore as every value lies within the maximum possible range. If the query range uses exclusive boundaries the query won't be rewritten as a field could contain a value being `Long.MIN_VALUE` or `Long.MAX_VALUE` which wouldn't match anymore. I've made `LongValuesSource.FieldValuesSource` and `MultiLongValuesSource.FieldMultiValueSource` public and added a corresponding `getField` accessor which will be needed to check, whether the value source is actually relying on the specific field. I'll plan to open a separate PR for `DoubleRange` performing a similar optimization. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
