[
https://issues.apache.org/jira/browse/LUCENE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209267#comment-13209267
]
Robert Muir commented on LUCENE-3792:
-------------------------------------
{quote}
If you don't run those through a query analyzer (e.g. generally produce
TermQuery directly) then you have lots of additional work.
{quote}
Thats not true, because keywordanalyzer does nothing to the terms, you can
continue to produce termquery directly and it will work.
So expert users are fine.
This issue isnt about expert users, its about how our API traps people that are
not expert users.
> 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: [email protected]
For additional commands, e-mail: [email protected]
