[
https://issues.apache.org/jira/browse/LUCENE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-3792:
---------------------------------
Fix Version/s: (was: 4.7)
4.8
> Remove StringField
> ------------------
>
> Key: LUCENE-3792
> URL: https://issues.apache.org/jira/browse/LUCENE-3792
> Project: Lucene - Core
> Issue Type: Task
> Affects Versions: 4.0-ALPHA
> Reporter: Robert Muir
> Fix For: 4.8
>
> Attachments: LUCENE-3792_javadocs_3x.patch,
> LUCENE-3792_javadocs_3x.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
