[
https://issues.apache.org/jira/browse/SOLR-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788110#comment-13788110
]
Nathan Neulinger commented on SOLR-5307:
----------------------------------------
In my case, I have a dynamic set of collections, so I started everything up
with collection1 that is essentially unused, and only exists for the sake of
bringing the cluster up and online. Based on that, if other issue didn't do
that bootstrap, I can certainly see the issues being the same.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
