+1 I've lost count of the number of times people on the user's list have used the string type and wondered why searches on terms in the field didn't work.
Erick On Sun, Sep 9, 2012 at 6:46 PM, Chris Male (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/LUCENE-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451730#comment-13451730 > ] > > Chris Male commented on LUCENE-4369: > ------------------------------------ > > I'm +1 for renaming this field (and even considering its long term future) > I'm just not sure how MatchOnlyField conveys the fact it bypasses analysis? > >> 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 >> >> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
