[jira] [Commented] (SOLR-10908) CloudSolrStream.toExpression incorrectly handles fq clauses

2017-08-16 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-10908) CloudSolrStream.toExpression incorrectly handles fq clauses

2017-08-14 Thread Erick Erickson (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126422#comment-16126422
 ] 

Erick Erickson commented on SOLR-10908:
---

Done.

> 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] [Commented] (SOLR-10908) CloudSolrStream.toExpression incorrectly handles fq clauses

2017-08-14 Thread Varun Thacker (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-10908) CloudSolrStream.toExpression incorrectly handles fq clauses

2017-07-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086283#comment-16086283
 ] 

ASF subversion and git services commented on SOLR-10908:


Commit 4080791e0a7eedd5d108a5096be0d2cfaea008d6 in lucene-solr's branch 
refs/heads/branch_6x from [~erickerickson]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4080791 ]

commit 4241a13beb0a14e8bd81a520bd8e04ab6c7465aa
Author: Erick Erickson 
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-10908) CloudSolrStream.toExpression incorrectly handles fq clauses

2017-07-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086271#comment-16086271
 ] 

ASF subversion and git services commented on SOLR-10908:


Commit fbc3d31f1bab7616ea631cf645923d09ef8123f3 in lucene-solr's branch 
refs/heads/branch_7_0 from [~erickerickson]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=fbc3d31 ]

commit 4241a13beb0a14e8bd81a520bd8e04ab6c7465aa
Author: Erick Erickson 
Date:   Thu Jul 13 10:39:33 2017 -0700

SOLR-10908: CloudSolrStream.toExpression incorrectly handles fq clauses

(cherry picked from commit 19fd95b46cf40fa0b91b7dcf0b157706ea718efb)


> 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] [Commented] (SOLR-10908) CloudSolrStream.toExpression incorrectly handles fq clauses

2017-07-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (SOLR-10908) CloudSolrStream.toExpression incorrectly handles fq clauses

2017-07-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086168#comment-16086168
 ] 

ASF subversion and git services commented on SOLR-10908:


Commit 19fd95b46cf40fa0b91b7dcf0b157706ea718efb in lucene-solr's branch 
refs/heads/master from [~erickerickson]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=19fd95b ]

commit 4241a13beb0a14e8bd81a520bd8e04ab6c7465aa
Author: Erick Erickson 
Date:   Thu Jul 13 10:39:33 2017 -0700

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
> 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