You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2016/05/03 23:20:12 UTC
[jira] [Created] (SOLR-9063) CloudSolrClient with _route_ shouldn't
require collection param to disambig cores
David Smiley created SOLR-9063:
----------------------------------
Summary: CloudSolrClient with _route_ shouldn't require collection param to disambig cores
Key: SOLR-9063
URL: https://issues.apache.org/jira/browse/SOLR-9063
Project: Solr
Issue Type: Bug
Components: SolrCloud, SolrJ
Affects Versions: 4.10.4
Reporter: David Smiley
CloudSolrClient uses {{\_route\_}} to know where to send a request It sorta works -- it'll go to an appropriate _node_. But it will only go to the correct core on that node if the {{collection}} parameter is explicitly added. In another words, it ignores the default collection configured on CloudSolrClient. It also seems to ignore "collection" parameter to the protected method sendRequest for this purpose too. As I write this, see line 1139 on master.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org