I've run into an orchestration problem while creating collections and loading plugins via the ConfigAPI in Solr Cloud.
Here's the scenario: 1. I create a configSet that references a custom class in schema.xml. 2. I upload the jar to the BlobStore and issue add-runtimelib using the Config API. This fails because the collection doesn't exist yet. 3. I try to create the collection with the configSet but it fails because the custom plugin is not available yet. I can force this to work by removing the custom reference, create the collection, load the jar and then add the custom reference back in place. This is fine as a manual one-time setup, but not feasible in a scripted production deployment. I wish I could create a collection without actually needing to create any cores. Then, I could get all of the configurations for a collection setup before creating the cores. -- View this message in context: http://lucene.472066.n3.nabble.com/Can-t-create-collection-without-plugin-can-t-load-plugin-without-collection-tp4294865.html Sent from the Solr - User mailing list archive at Nabble.com.
