gsmiller commented on issue #13840: URL: https://github.com/apache/lucene/issues/13840#issuecomment-2402588570
@iverase I wonder if moving the logic is the right thing to do vs. having the optimization in both places? I suspect the most likely way `IndexSortSortedNumericDocValuesRangeQuery` gets created is through the `IntField/LongField#newRangeQuery` method, which assumes the numeric field is indexed both with points and doc values. While that is probably the most common scenario, if users aren't indexing points and directly leveraging `NumericDocValues/SortedNumericDocValues#newSlowRangeQuery` it would be nice for them to also get this 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
