[
https://issues.apache.org/jira/browse/SOLR-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788107#comment-13788107
]
Erick Erickson commented on SOLR-5307:
--------------------------------------
Right, might you have had the default collection already on your system so you
were able to find the configuration set for collection1 even though you didn't
want to? Under any circumstances it smells like these two issues are related...
Thanks for the clarification...
> Solr 4.5 collection api ignores collection.configName when used in cloud
> ------------------------------------------------------------------------
>
> Key: SOLR-5307
> URL: https://issues.apache.org/jira/browse/SOLR-5307
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.5
> Reporter: Nathan Neulinger
> Labels: cloud, collection-api, zookeeper
>
> This worked properly in 4.4, but on 4.5, specifying collection.configName
> when creating a collection doesn't work - it gets the default regardless of
> what has been uploaded into zk. Explicitly linking config name to collection
> ahead of time with zkcli.sh is a workaround I'm using for the moment, but
> that did not appear to be necessary with 4.4 unless I was doing something
> wrong and not realizing it.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
