lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Toomey (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-4983) Problematic core naming by collection create API
Date Tue, 02 Jul 2013 01:51:21 GMT
Chris Toomey created SOLR-4983:
----------------------------------

             Summary: Problematic core naming by collection create API 
                 Key: SOLR-4983
                 URL: https://issues.apache.org/jira/browse/SOLR-4983
             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 https://issues.apache.org/jira/browse/SOLR-4905 and http://lucene.472066.n3.nabble.com/Joins-with-SolrCloud-tp4073199p4074038.html,
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message