lucene-dev mailing list archives

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

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

Uwe Schindler commented on LUCENE-3792:
---------------------------------------

bq. Well we are at a standstill. We constantly get these problems on the users list from NOT_ANALYZED

You cannot prevent users from doing the wrong thing. If you remove StringField completely,
pleaese also remove NumericField and force users to use PerFieldAnalyzerWrapper with a NumericTokenStream.
If you add a numeric field you cannot ask for it with query parser. If you add a StringField,
you cann ask with QueryParser. Simple rule. It must just be clearly documented. And possible
StringField renamed.

People using primary keys or other untokenized values should simply not use QueryParser. Use
a ComstantScoreTermyQuery and you are fine.

This is all just a documentation problem, so I am completely against removing that. Not everybody
is using Lucene purely as a full-text engine.
                
> 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