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 DC7D69EC5 for ; Fri, 25 May 2012 15:00:27 +0000 (UTC) Received: (qmail 54182 invoked by uid 500); 25 May 2012 15:00:26 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 54125 invoked by uid 500); 25 May 2012 15:00:26 -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 54112 invoked by uid 99); 25 May 2012 15:00:26 -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 15:00:26 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 49F77142815 for ; Fri, 25 May 2012 15:00:26 +0000 (UTC) Date: Fri, 25 May 2012 15:00:26 +0000 (UTC) From: "Yonik Seeley (JIRA)" To: dev@lucene.apache.org Message-ID: <276696982.2488.1337958026305.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1829634297.1410.1337946023893.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Comment Edited] (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=13283510#comment-13283510 ] Yonik Seeley edited comment on SOLR-3488 at 5/25/12 2:58 PM: ------------------------------------------------------------- bq. should we instead add a create node to a queue in zookeeper? Yeah, a work queue in ZK makes perfect sense. Perhaps serialize the params to a JSON map/object per line? edit: or perhaps it makes more sense for each operation to be a separate file (which is what I think you wrote anyway) Possible parameters: - name of the collection - the config for the collection - number of shards in the new collection - default replication factor Operations: - add a collection - remove a collection - different options here... leave cores up, bring cores down, completely remove cores (and data) - change collection properties (replication factor, config) - expand collection (split shards) - add/remove a collection alias Shard operations: - add a shard (more for custom sharding) - remove a shard - change shard properties (replication factor) - split a shard - add/remove a shard alias was (Author: yseeley@gmail.com): bq. should we instead add a create node to a queue in zookeeper? Yeah, a work queue in ZK makes perfect sense. Perhaps serialize the params to a JSON map/object per line? Possible parameters: - name of the collection - the config for the collection - number of shards in the new collection - default replication factor Operations: - add a collection - remove a collection - different options here... leave cores up, bring cores down, completely remove cores (and data) - change collection properties (replication factor, config) - expand collection (split shards) - add/remove a collection alias Shard operations: - add a shard (more for custom sharding) - remove a shard - change shard properties (replication factor) - split a shard - add/remove a shard alias > 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