[
https://issues.apache.org/jira/browse/SOLR-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166361#comment-13166361
]
Yonik Seeley commented on SOLR-2957:
------------------------------------
Lookup core name directy as is done now.
If it's not found, and we are in ZK mode, then
return the core for a shard leader in the collection one exists, or
return the core for any shard in the collection.
What about the case where there isn't even a shard for the collection being
requested?
It would seem desirable for a client to be able to hit any node in a cluster
w/o worrying about layout, movement, and rebalancing making requests suddenly
fail.
One solution: if there's not a local core for the collection, convert the URL
to add the collection name as a parameter and then return the default core,
which can then do the appropriate forwarding logic.
> collection URLs in a cluster
> ----------------------------
>
> Key: SOLR-2957
> URL: https://issues.apache.org/jira/browse/SOLR-2957
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud, update
> Reporter: Yonik Seeley
> Fix For: 4.0
>
>
> In solrcloud, one can hit a URL of /collection1/select and get a distributed
> search over collection1.
> If we wish to maintain this, we'll need some more flexible URL to core
> mapping since there may be more than one core for the collection on a node,
> and the "collection1" core on that node could go away altogether.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
