Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Tue, 11 Sep 2012 22:48:07 +1100 (NCT)
From: "Uwe Schindler (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <1388810704.62903.1347364087918.JavaMail.jiratomcat@arcas>
In-Reply-To: <950365474.55973.1347219907853.JavaMail.jiratomcat@arcas>
Subject: [jira] [Comment Edited] (LUCENE-4369) StringFields name is
 unintuitive and not helpful
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LUCENE-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452945#comment-13452945 ] 

Uwe Schindler edited comment on LUCENE-4369 at 9/11/12 10:48 PM:
-----------------------------------------------------------------

bq. We don't need to rush it, I think its fairly contained to change, we don't even have to deal with this for 4.0 if we aren't happy: we can deprecate StringField just have it extend XXXField in a future 4.x release too.

I am against this, we should change this before Lucene 4.0. We have seen already on user list that many people understand it wrong, so for me this issue is a "Blocker" for 4.0.
                
      was (Author: thetaphi):
    bq. We don't need to rush it, I think its fairly contained to change, we don't even have to deal with this for 
4.0 if we aren't happy: we can deprecate StringField just have it extend XXXField in a future 4.x release too.

I am against this, we should change this before Lucene 4.0. We have seen already on user list that many people understand it wrong, so for me this issue is a "Blocker" for 4.0.
                  
> StringFields name is unintuitive and not helpful
> ------------------------------------------------
>
>                 Key: LUCENE-4369
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4369
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>         Attachments: LUCENE-4369.patch
>
>
> There's a huge difference between TextField and StringField, StringField screws up scoring and bypasses your Analyzer.
> (see java-user thread "Custom Analyzer Not Called When Indexing" as an example.)
> The name we use here is vital, otherwise people will get bad results.
> I think we should rename StringField to MatchOnlyField.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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