[LUCENE-831] Complete overhaul of FieldCache API/Implementation

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 4.9, 6.0
• Component/s: core/search
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Chris M. Hostetter
• Created: 14/Mar/07 07:25
• Updated: 28/Aug/22 11:35

Description

Motivation:
1) Complete overhaul the API/implementation of "FieldCache" type things...
a) eliminate global static map keyed on IndexReader (thus
eliminating synch block between completley independent IndexReaders)
b) allow more customization of cache management (ie: use
expiration/replacement strategies, disk backed caches, etc)
c) allow people to define custom cache data logic (ie: custom
parsers, complex datatypes, etc... anything tied to a reader)
d) allow people to inspect what's in a cache (list of CacheKeys) for
an IndexReader so a new IndexReader can be likewise warmed.
e) Lend support for smarter cache management if/when
IndexReader.reopen is added (merging of cached data from subReaders).
2) Provide backwards compatibility to support existing FieldCache API with
the new implementation, so there is no redundent caching as client code
migrades to new API.

Issue Links

• is related to: LUCENE-3390 Incorrect sort by Numeric values for documents missing the sorting field
• is related to: LUCENE-2133 [PATCH] IndexCache: Refactoring of FieldCache, FieldComparator, SortField
• is related to: LUCENE-1582 Make TrieRange completely independent from Document/Field with TokenStream of prefix encoded values
• relates to: LUCENE-1231 Column-stride fields (aka per-document Payloads)
• relates to: LUCENE-2665 Rework FieldCache to be more flexible/general
• relates to: LUCENE-1372 Proposal: introduce more sensible sorting when a doc has multiple values for a term
• relates to: LUCENE-743 IndexReader.reopen()