You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2017/08/14 21:04:00 UTC
[jira] [Commented] (SOLR-10908) CloudSolrStream.toExpression
incorrectly handles fq clauses
[ https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126390#comment-16126390 ]
Varun Thacker commented on SOLR-10908:
--------------------------------------
Hi Erick,
Should we remove the 7.1 entry from the Fix/Versions as it's there in 7.0 already?
> 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), 7.1
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org