[
https://issues.apache.org/jira/browse/LUCENE-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455825#comment-13455825
]
Michael McCandless commented on LUCENE-4369:
--------------------------------------------
I prefer ExactTextField over Untokenized (or UnAnalyzed) Field,
because that name matches the typical use-case of this field: you want
to index exactly the text value so you can later retrieve by that
value.
Yes, the field is untokenized, but this is something of an
implementation detail: that's just how it achieves exact matching.
And it's only one of the things it does (it also turns off norms, sets
DOCS_ONLY).
In general I think we should name things according to how they are
most likely to be used, not according to how they are implemented.
The goal here isn't to find a name that everybody loves ... only to
find one that nobody hates ... and I think ExactTextField is a big
improvement over StringField.
> 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]
