lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Toomey (JIRA)" <>
Subject [jira] [Commented] (SOLR-4983) Problematic core naming by collection create API
Date Thu, 05 Dec 2013 16:32:35 GMT


Chris Toomey commented on SOLR-4983:

Right, 2) is the real problem.  For 1) I doubt many would argue that "<collection_name>"
wouldn't be cleaner/prettier/less-surprising than "<collection_name>_shard<x>_replica<y>"
for the core names, but if that's not also achievable when addressing 2), that's fine..

> Problematic core naming by collection create API 
> -------------------------------------------------
>                 Key: SOLR-4983
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>            Reporter: Chris Toomey
> The SolrCloud collection create API creates cores named "foo_shard<x>_replica<y>"
when asked to create collection "foo".
> This is problematic for at least 2 reasons: 
> 1) these ugly core names show up in the core admin UI, and will vary depending on which
node is being used,
> 2) it prevents collections from being used in SolrCloud joins, since join takes a core
name as the fromIndex parameter and there's no single core name for the collection.  As I've
documented in and,
SolrCloud join does work when the inner collection (fromIndex) is not sharded, assuming that
collection is available and initialized at SolrCloud bootstrap time.
> Could this be changed to instead use the collection name for the core name?  Or at least
add a core-name option to the API?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message