Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B5E9C036 for ; Fri, 25 May 2012 13:32:25 +0000 (UTC) Received: (qmail 42615 invoked by uid 500); 25 May 2012 13:32:23 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 42559 invoked by uid 500); 25 May 2012 13:32:23 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 42550 invoked by uid 99); 25 May 2012 13:32:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 May 2012 13:32:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 76ACE1418B6 for ; Fri, 25 May 2012 13:32:23 +0000 (UTC) Date: Fri, 25 May 2012 13:32:23 +0000 (UTC) From: "Mark Miller (JIRA)" To: dev@lucene.apache.org Message-ID: <647457022.1840.1337952743490.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1829634297.1410.1337946023893.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (SOLR-3488) Create a Collections API for SolrCloud MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283382#comment-13283382 ] Mark Miller commented on SOLR-3488: ----------------------------------- 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