[ https://issues.apache.org/jira/browse/SOLR-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955055#comment-14955055 ]
Erik Hatcher commented on SOLR-8160: ------------------------------------ With this change, it effectively makes it a "fields" query parser, like "term"/"field". I wonder if we should keep "terms" as-is, and add a "fields" query parser? (though I can't imagine a scenario where I wouldn't want the field type analysis to apply when using terms, though I'd also pretty much always use a string field type) > Terms query parser should optionally do query analysis > ------------------------------------------------------- > > Key: SOLR-8160 > URL: https://issues.apache.org/jira/browse/SOLR-8160 > Project: Solr > Issue Type: Improvement > Components: query parsers, search > Affects Versions: 5.3 > Reporter: Devansh Dhutia > > Field setup as > {code} > <field name="cs" type="string_ci" indexed="true" stored="true" > multiValued="false" required="false" /> > <fieldType name="string_ci" class="solr.TextField" sortMissingLast="true"> > <analyzer type="index"> > <tokenizer class="solr.KeywordTokenizerFactory" /> > <filter class="solr.LowerCaseFilterFactory" /> > </analyzer> > <analyzer type="query"> > <tokenizer class="solr.KeywordTokenizerFactory" /> > <filter class="solr.LowerCaseFilterFactory" /> > </analyzer> > </fieldType> > {code} > Value sent to cs field for indexing include: AA, BB > Following is observed > {code}&fq={!terms f=cs}AA,BB{code} yields 0 results > {code}&fq={!terms f=cs}aa,bb{code} yields 2 results > {code}&fq=cs:(AA BB){code} yields 2 results > {code}&fq=cs:(aa bb){code} yields 2 results > The first variant above should behave like the other 3 & obey query time > analysis -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org