[LUCENE-1701] Add NumericField, make plain text numeric parsers public in FieldCache, move trie parsers to FieldCache

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9
• Fix Version/s: 2.9
• Component/s: core/index, core/search
• Lucene Fields: New
• Assignee: Uwe Schindler
• Reporter: Uwe Schindler
• Created: 19/Jun/09 13:28
• Updated: 28/Aug/22 12:02
• Resolved: 23/Jun/09 15:43

Description

In discussions about LUCENE-1673, Mike & me wanted to add a new NumericField to o.a.l.document specific for easy indexing. An alternative would be to add a NumericUtils.newXxxField() factory, that creates a preconfigured Field instance with norms and tf off, optionally a stored text (LUCENE-1699) and the TokenStream already initialized. On the other hand NumericUtils.newXxxSortField could be moved to NumericSortField.

I and Yonik tend to use the factory for both, Mike tends to create the new classes.

Also the parsers for string-formatted numerics are not public in FieldCache. As the new SortField API (LUCENE-1478) makes it possible to support a parser in SortField instantiation, it would be good to have the static parsers in FieldCache public available. SortField would init its member variable to them (instead of NULL), so making code a lot easier (FieldComparator has this ugly null checks when retrieving values from the cache).

Moving the Trie parsers also as static instances into FieldCache would make the code cleaner and we would be able to hide the "hack" StopFillCacheException by making it private to FieldCache (currently its public because NumericUtils is in o.a.l.util).

Issue Links

• incorporates: LUCENE-1687 Remove ExtendedFieldCache by rolling functionality into FieldCache
• relates to: LUCENE-1673 Move TrieRange to core
• relates to: SOLR-940 TrieRange support
• relates to: LUCENE-1699 Field tokenStream should be usable with stored fields.