lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-3488) Create a Collections API for SolrCloud
Date Fri, 25 May 2012 15:13:23 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283382#comment-13283382
] 

Mark Miller edited comment on SOLR-3488 at 5/25/12 3:12 PM:
------------------------------------------------------------

I'll post an initial patch just for create soon. It's just a start though. I've added a bunch
of comments for TODOs or things to consider for the future. I'd like to start simple just
to get 'something' in though.

So initially, you can create a new collection and pass an existing collection name to determine
which shards it's created on. Would also be nice to be able to explicitly pass the shard urls
to use, as well as simply offer X shards, Y replicas. In that case, perhaps the -leader- overseer
could handle ensuring that. You might also want to be able to simply say, create it on all
known shards.

Further things to look at:

* other commands, like remove/delete.
* what to do when some create calls fail? should we instead add a create node to a queue in
zookeeper? Make the overseer responsible for checking for any jobs there, completing them
(if needed) and then removing the job from the queue? Other ideas.
                
      was (Author: markrmiller@gmail.com):
    I'll post an initial patch just for create soon. It's just a start though. I've added
a bunch of comments for TODOs or things to consider for the future. I'd like to start simple
just to get 'something' in though.

So initially, you can create a new collection and pass an existing collection name to determine
which shards it's created on. Would also be nice to be able to explicitly pass the shard urls
to use, as well as simply offer X shards, Y replicas. In that case, perhaps the leader could
handle ensuring that. You might also want to be able to simply say, create it on all known
shards.

Further things to look at:

* other commands, like remove/delete.
* what to do when some create calls fail? should we instead add a create node to a queue in
zookeeper? Make the overseer responsible for checking for any jobs there, completing them
(if needed) and then removing the job from the queue? Other ideas.
                  
> Create a Collections API for SolrCloud
> --------------------------------------
>
>                 Key: SOLR-3488
>                 URL: https://issues.apache.org/jira/browse/SOLR-3488
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>


--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message