[
https://issues.apache.org/jira/browse/LUCENE-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453317#comment-13453317
]
Steven Rowe commented on LUCENE-4369:
-------------------------------------
Serious suggestion: WholeTextField
(Following the raw/cooked food metaphor used in various computational contexts
- "whole food" means unprocessed.)
I like ExactTextField too, but it's missing the beginning and end anchors: the
intent is "exactly this search string", but it doesn't necessarily imply "and
nothing else". E.g. would a user armed only with the name assume that an
ExactTextField query string "two three" would not match an indexed string "one
two three four"?
> 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: [email protected]
For additional commands, e-mail: [email protected]
