[
https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086175#comment-16086175
]
ASF subversion and git services commented on SOLR-10908:
--------------------------------------------------------
Commit b7e52db2d49f9e43cdd3ac245ad2b363a66518ca in lucene-solr's branch
refs/heads/branch_7x from [~erickerickson]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b7e52db ]
commit 4241a13beb0a14e8bd81a520bd8e04ab6c7465aa
Author: Erick Erickson <[email protected]>
Date: Thu Jul 13 10:39:33 2017 -0700
SOLR-10908: CloudSolrStream.toExpression incorrectly handles fq clauses
(cherry picked from commit 19fd95b)
> 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
> 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]
