[LUCENE-3792] Remove StringField

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.0-ALPHA
• Fix Version/s: 4.9, 6.0
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Robert Muir
• Created: 16/Feb/12 10:20
• Updated: 28/Aug/22 13:08

Description

Often on the mailing list there is confusion about NOT_ANALYZED.

Besides being useless (Just use KeywordAnalyzer instead), people trip up on this
not being consistent at query time (you really need to configure KeywordAnalyzer for the field
on your PerFieldAnalyzerWrapper so it will do the same thing at query time... oh wait
once you've done that, you dont need NOT_ANALYZED).

So I think StringField is a trap too for the same reasons, just under a
different name, lets remove it.

Issue Links

• is superceded by: LUCENE-4369 StringFields name is unintuitive and not helpful