[jira] [Updated] (LUCENE-3792) Remove StringField

["Robert Muir (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir updated LUCENE-3792:
--------------------------------

             Priority: Blocker  (was: Major)
    Affects Version/s: 4.0
        Fix Version/s: 4.0

Setting this as blocker (sorry).

Its a huge trap when someone sets the same Analyzer on IndexWriter and QueryParser
but the analysis isn't "actually the same".
                
> 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
>            Priority: Blocker
>             Fix For: 4.0
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org