[jira] [Updated] (SOLR-10908) CloudSolrStream.toExpression incorrectly handles fq clauses
[ https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson updated SOLR-10908: -- Fix Version/s: 7.1 6.6.1 > 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, 6.6.1, 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10908) CloudSolrStream.toExpression incorrectly handles fq clauses
[ https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson updated SOLR-10908: -- Fix Version/s: (was: 7.1) > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10908) CloudSolrStream.toExpression incorrectly handles fq clauses
[ https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson updated SOLR-10908: -- Attachment: SOLR-10908.patch Final patch with CHANGES.txt > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10908) CloudSolrStream.toExpression incorrectly handles fq clauses
[ https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson updated SOLR-10908: -- Summary: CloudSolrStream.toExpression incorrectly handles fq clauses (was: CloudSolrStream.toExpression (and perhaps others) 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 > Attachments: SOLR-10229.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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
