Collection API wrong configuration
I'm experimenting with SolrCloud using Solr 4.5.0 and the Collection API What i did was: 1. upload configuration to ZK zkcli.sh -cmd upconfig -zkhost 127.0.0.1:8993 -d solr/my_custom_collection/conf/ -n my_custom_collection 2. create a collection using the api: /admin/collections?action=CREATEname=my_custom_collectionnumShards=2replicationFactor=2maxShardsPerNode=2collection.configName=my_custom_config The outcome of these action seem to be that the collection cores don't use the my_custom_collection but the example configuration. Any idea why this is happening? -- View this message in context: http://lucene.472066.n3.nabble.com/Collection-API-wrong-configuration-tp4094319.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Collection API wrong configuration
Using Solr 4.4.0 the same scenarion behaves as expected. Can anyone else try this, to check if it this only happens with 4.5.0 and if so, is this a desired behaviour or a bug? -- View this message in context: http://lucene.472066.n3.nabble.com/Collection-API-wrong-configuration-tp4094319p4094323.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Collection API wrong configuration
This may be a bug in 4.5 Another user has also reported this bug: https://issues.apache.org/jira/browse/SOLR-5307 On Wed, Oct 9, 2013 at 3:51 PM, maephisto my_sky...@yahoo.com wrote: Using Solr 4.4.0 the same scenarion behaves as expected. Can anyone else try this, to check if it this only happens with 4.5.0 and if so, is this a desired behaviour or a bug? -- View this message in context: http://lucene.472066.n3.nabble.com/Collection-API-wrong-configuration-tp4094319p4094323.html Sent from the Solr - User mailing list archive at Nabble.com. -- Regards, Shalin Shekhar Mangar.
Re: Collection API wrong configuration
Works fine at my end. I use Solr 4.5.0 on Windows 7. I tried: zkcli.bat -cmd upconfig -zkhost localhost:9000 -d ..\solr\collection2\conf -n my_custom_collection java -Djetty.port=8001 -DzkHost=localhost:9000 -jar start.jar and finally http://localhost:8001/solr/admin/collections?action=CREATEname=my_custom_collectionnumShards=1replicationFactor=1maxShardsPerNode=1collection.configName=my_custom_collection If I open newly created core/shard I can see under Schema the modified schema file. Best regards, Primož From: maephisto my_sky...@yahoo.com To: solr-user@lucene.apache.org Date: 09.10.2013 11:57 Subject:Collection API wrong configuration I'm experimenting with SolrCloud using Solr 4.5.0 and the Collection API What i did was: 1. upload configuration to ZK zkcli.sh -cmd upconfig -zkhost 127.0.0.1:8993 -d solr/my_custom_collection/conf/ -n my_custom_collection 2. create a collection using the api: /admin/collections?action=CREATEname=my_custom_collectionnumShards=2replicationFactor=2maxShardsPerNode=2collection.configName=my_custom_config The outcome of these action seem to be that the collection cores don't use the my_custom_collection but the example configuration. Any idea why this is happening? -- View this message in context: http://lucene.472066.n3.nabble.com/Collection-API-wrong-configuration-tp4094319.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Collection API wrong configuration
Yes, the problem described in the ticket is what I'm also confronting with. -- View this message in context: http://lucene.472066.n3.nabble.com/Collection-API-wrong-configuration-in-4-5-0-tp4094319p4094335.html Sent from the Solr - User mailing list archive at Nabble.com.
