lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (LUCENE-3792) Remove StringField
Date Thu, 16 Feb 2012 10:46:59 GMT

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

Uwe Schindler edited comment on LUCENE-3792 at 2/16/12 10:46 AM:
-----------------------------------------------------------------

The backside of this is now, that you need to explicitely use a KeywordAnalyzer now for Primary
Key fields. If you don't run those through a query analyzer (e.g. generally produce TermQuery
directly) then you have lots of additional work. For simple "lookup" queries and indexing
a PK key, this is a no go.

-1 on removing that completely, it should simply called different. We should maybe add PKQuery
(a ConstantScore TermQuery) and PKField to have a symmetry.
                
      was (Author: thetaphi):
    The backside of this is now, that you need to explicitely use a KeywordAnalyzer now for
Primary Key fields. If you don't run those through a query analyzer (e.g. generally produce
TermQuery directly) then you have lots of additional work. For simple "lookup" queries and
indexing a PK key, this is a no go.

-1 on removing that completely, it should simply called different. We should maybe add PKQuery
and PKField to have a symmetry.
                  
> 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


Mime
View raw message