HoustonPutman commented on PR #16629: URL: https://github.com/apache/lucene/pull/16629#issuecomment-5545826597
Yeah I thought about keeping `NumericFieldStats`, but it just got complicated. Because if the class is intended to be used by points and if the class is intended to be used by docValues, they need to return different data. So you need a decoder and encoder for both docValues and points. Or at least a bi-directional encoder. Which, just seems complex. As I said in the issue, it would be amazing if we could enforce changing NumericDocValues to require sorted-order longs (like SortedDocValues does), and then we could really start to reason the same between Points and Numeric/SortedNumeric docValues. But that would be a really big (back-compat-breaking) change even for a major version. @romseygeek good point about `IndexSortSortedNumericDocValuesRangeQuery`. We kind of have to revert the functionality unless we know the docValues are in fact SortedNumeric not Numeric. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
