[SOLR-4140] Collection API: CloudSolrServer cannot be used to create collection without referencing an existing collection

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.0
• Fix Version/s: 4.1, 6.0
• Component/s: multicore, SolrCloud
• Labels: collection-api multicore
• Assignee: Mark Miller
• Reporter: Per Steffensen
• Created: 03/Dec/12 14:43
• Updated: 09/May/16 18:55
• Resolved: 13/Dec/12 03:46

Description

CloudSolrServer needs an existing collection to be able to forward requests. For some requests it is not logical that you ned to have or reference an existing collection. E.g. if you want to use CloudSolrServer to create a collection - especially:

• If you have no collections already and want to create your first collection
• If you like to create your CloudSolrServer once and for all, and want to set default-collection on it to point to your favorite collection, but also use this CloudSolrServer to create this favorite collection

Yes, HttpSolrServer can be used, but

• Some of us like to use CloudSolrServer for everything
• Using HttpSolrServer you need to check youself which nodes are running, in order to send the create-request to one of them

Issue Links

• is related to: SOLR-3425 CloudSolrServer can't create cores when using the zkHost based constructor