Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ADC2ADC41 for ; Wed, 27 Jun 2012 15:40:45 +0000 (UTC) Received: (qmail 99741 invoked by uid 500); 27 Jun 2012 15:40:45 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 99657 invoked by uid 500); 27 Jun 2012 15:40:45 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 99641 invoked by uid 99); 27 Jun 2012 15:40:45 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2012 15:40:45 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id C9898142865 for ; Wed, 27 Jun 2012 15:40:44 +0000 (UTC) Date: Wed, 27 Jun 2012 15:40:44 +0000 (UTC) From: "Brandon Williams (JIRA)" To: commits@cassandra.apache.org Message-ID: <480168408.62259.1340811644827.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1158275304.62207.1340810323970.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (CASSANDRA-4381) Add an initial_schema option 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/CASSANDRA-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402298#comment-13402298 ] Brandon Williams commented on CASSANDRA-4381: --------------------------------------------- Given CASSANDRA-2963, do we really need this? In particular typing in a uuid sounds error prone and tedious vs resetting the 'bad' node. > Add an initial_schema option > ---------------------------- > > Key: CASSANDRA-4381 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4381 > Project: Cassandra > Issue Type: Improvement > Affects Versions: 1.0.0 > Reporter: Joaquin Casares > Priority: Minor > Labels: lhf > Fix For: 1.1.2 > > > Just like the initial_token option, we can have an option that lists the initial schema we want a node to read. > This comes in handy in situations where multiple nodes have schema disagreements, even if split between 2 or more schemas. > This can be a hidden option, but would be nice to see in rare cases, especially since I've been noticing that schema disagreement resolution has been taking more than one round of restarts lately. -- 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