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=CREATE&name=my_custom_collection&numShards=1&replicationFactor=1&maxShardsPerNode=1&collection.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=CREATE&name=my_custom_collection&numShards=2&replicationFactor=2&maxShardsPerNode=2&collection.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.
