[
https://issues.apache.org/jira/browse/SOLR-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136611#comment-18136611
]
David Smiley commented on SOLR-8160:
------------------------------------
We could devise a contrived back-wards compatibility break but what about
something practical? Firstly, most cases is using this on a String field, so
the setting is irrelevant for such. Let's say it's an analyzed field... then
IMO it's _very very_ likely that the term given will be unchanged if analyzed
again. Challenge me on this if you think otherwise with a realistic
config/scenario.
> 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
> Assignee: David Smiley
> Priority: Major
>
> 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
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
