Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 73B3ED0F2 for ; Tue, 11 Sep 2012 11:50:12 +0000 (UTC) Received: (qmail 7274 invoked by uid 500); 11 Sep 2012 11:50:10 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 7172 invoked by uid 500); 11 Sep 2012 11:50:10 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 6735 invoked by uid 99); 11 Sep 2012 11:50:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2012 11:50:09 +0000 Date: Tue, 11 Sep 2012 22:50:09 +1100 (NCT) From: "Robert Muir (JIRA)" To: dev@lucene.apache.org Message-ID: <1934568627.62924.1347364209441.JavaMail.jiratomcat@arcas> In-Reply-To: <950365474.55973.1347219907853.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (LUCENE-4369) StringFields name is unintuitive and not helpful MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LUCENE-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452947#comment-13452947 ] Robert Muir commented on LUCENE-4369: ------------------------------------- {quote} The problem with ExactMatch field is: If it is also stored, the name is misleasing again, so KeywordField is better. {quote} I dont understand how storing is related. storing is the same always. {quote} If we would 100% differentiate between stored and indexed fields while indexing (requiring that the field is also added 2 times, one time as indexed and one time as indexed), I would be fine with "MatchOnlyField" and "StoredStringField". {quote} In my opinion the only thing worse we could do to our .document API than StringField would be to require the user to add the field twice. > 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