[
https://issues.apache.org/jira/browse/LUCENE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209290#comment-13209290
]
Uwe Schindler commented on LUCENE-3792:
---------------------------------------
I am fine with that. As I said: We need correct documentation to prevent traps.
But removing traps by removing possibilities is the wrong way to go. It will
force users to have crazy code for simple things, thats my problem. I don't use
QueryParser, so I don't want solutions prefering QueryParser over anything
else. QueryParser is just a convenience API around new BQ()...new TQ... E.g., I
have my own query parser (and I suggest everybody else to have the same for
user-facing queries) that simply analyzes the text and creates a BQ out of all
anaylzed terms. No syntax, nothing. And I only execute that one on the field in
question. Thats very simplistic but another way to look on things.
> 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
> Fix For: 4.0
>
> Attachments: LUCENE-3792_javadocs_3x.patch,
> LUCENE-3792_javadocs_3x.patch
>
>
> 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]
