[
https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129356#comment-16129356
]
ASF subversion and git services commented on SOLR-10908:
--------------------------------------------------------
Commit 8547474c8ad815baf352cb86d4b1618d7dc5ac8b in lucene-solr's branch
refs/heads/branch_6_6 from Erick
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8547474 ]
SOLR-10908: CloudSolrStream.toExpression incorrectly handles fq clauses
> CloudSolrStream.toExpression incorrectly handles fq clauses
> -----------------------------------------------------------
>
> Key: SOLR-10908
> URL: https://issues.apache.org/jira/browse/SOLR-10908
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.6, 7.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Fix For: 7.0, 6.7, master (8.0)
>
> Attachments: SOLR-10229.patch, SOLR-10908.patch, SOLR-10908.patch
>
>
> toExpression in at least CloudSolrStream concatenates parameters in a
> comma-separated list. This is fine for things like sorting but incorrect for
> fq clauses. If my input is something like
> fq=condition1
> fq=condition2
> it winds up being something like
> fq=condition1,condition2
> I've seen it in this class for this parameter, other classes and other
> parameters might have the same problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
