[ https://issues.apache.org/jira/browse/LUCENE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir updated LUCENE-3792: -------------------------------- Attachment: LUCENE-3792_javadocs_3x.patch Its obvious Uwe and I aren't going to agree here immediately, so here is a patch adding a big warning to 3.x javadocs. For now I'd like to apply the same warning to StringField in trunk (I just made the patch against 3.x) > Remove StringField > ------------------ > > Key: LUCENE-3792 > URL: https://issues.apache.org/jira/browse/LUCENE-3792 > Project: Lucene - Java > Issue Type: Task > Affects Versions: 4.0 > Reporter: Robert Muir > Fix For: 4.0 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org