[
https://issues.apache.org/jira/browse/SOLR-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953503#comment-14953503
]
Hoss Man commented on SOLR-8160:
TermsQParser is behaving as intended & documented...
https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-TermsQueryParser
bq. ... functions similarly to the Term Query Parser but takes in multiple
values separated by commas and returns documents matching any of the specified
values. This can be useful for generating filter queries from the external
human readable terms returned by the faceting or terms components, ...
Changing this behavior to involve query time analysis would be a new feature
request, and would need to be dependent on some other new localparam option to
indicate when it should be enabled.
> Terms query parser ignores query analysis
> --
>
> Key: SOLR-8160
> URL: https://issues.apache.org/jira/browse/SOLR-8160
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.3
>Reporter: Devansh Dhutia
>
> Field setup as
> {code}
> multiValued="false" required="false" />
>
>
>
>
>
>
>
>
>
>
> {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