[LUCENE-3312] Break out StorableField from IndexableField

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 6.0
• Component/s: core/index
• Labels: gsoc2012 lucene-gsoc-12
• Lucene Fields: New
• Assignee: Nikola Tankovic
• Reporter: Michael McCandless
• Created: 14/Jul/11 10:29
• Updated: 28/Aug/22 12:53
• Resolved: 02/Sep/12 14:38

Description

In the field type branch we have strongly decoupled
Document/Field/FieldType impl from the indexer, by having only a
narrow API (IndexableField) passed to IndexWriter. This frees apps up
use their own "documents" instead of the "user-space" impls we provide
in oal.document.

Similarly, with LUCENE-3309, we've done the same thing on the
doc/field retrieval side (from IndexReader), with the
StoredFieldsVisitor.

But, maybe we should break out StorableField from IndexableField,
such that when you index a doc you provide two Iterables – one for the
IndexableFields and one for the StorableFields. Either can be null.

One downside is possible perf hit for fields that are both indexed &
stored (ie, we visit them twice, lookup their name in a hash twice,
etc.). But the upside is a cleaner separation of concerns in API....

Issue Links

• is related to: LUCENE-4637 Using StringField for while storing becomes a regular Field when the document is retrieved - Due to this the next search cannot find the document because the value of the Field got tokenized which was not desired when it was added
• is superceded by: LUCENE-4347 Fix remaining issues with StorableField