[
https://issues.apache.org/jira/browse/LUCENE-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453174#comment-13453174
]
Michael McCandless commented on LUCENE-4369:
--------------------------------------------
I think it's useful to have a dedicated sugar field for things like primary
keys, URLs, enumerated fields ("country", "state", "zip code"), entitlements
fields (ACLs), tags, etc., and when users do this directly today I suspect they
often forget to disable norms and index with docs-only.
But I agree the name is trappy now.
+1 for ExactTextField. I don't really like "raw": it sounds too ... low level.
Like it's not even gonna be indexed or something.
> 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]
