You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2013/10/07 13:47:42 UTC
[jira] [Commented] (SOLR-5307) Solr 4.5 collection api ignores
collection.configName when used in cloud
[ https://issues.apache.org/jira/browse/SOLR-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788091#comment-13788091 ]
Erick Erickson commented on SOLR-5307:
--------------------------------------
Hmmm, is this the same thing as SOLR-5306? This is the second report of something with collections.configName. I'll link the two together, it seems like they should both be investigated together....
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org