HoustonPutman opened a new issue, #16580: URL: https://github.com/apache/lucene/issues/16580
### Description Under the hood, if a `SortedNumericDocValues` field is actually single-valued, then Lucene will store it as a single-valued `NumericDocValues` field and then wrap it to look like a SortedNumericDocValues field when accessed. Therefore, even though the utility classes `DoubleField`, `FloatField`, `LongField` and `IntField` use `SortedNumericDocValues` under the hood, these classes are still great when used with single-valued fields. For doubles and floats in particular, the sorted nature of the docValues representation make range queries better. (See https://github.com/apache/lucene/issues/16573 for one such reason) One big issue when changing to use this for single-valued fields is that you lose the ability to do docValues updates. There should be no issue supporting updates to single-valued `SortedNumericDocValues`, since ultimately it is a wrapped `NumericDocValues` (which supports updates). -- 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]
