Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <1411338423.7081270820631171.JavaMail.jira@brutus.apache.org>
Date: Fri, 9 Apr 2010 13:43:51 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-962) Schema definition propagation
 should happen before obtaining a bootstrap token.
In-Reply-To: <969401033.50731270670434274.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855395#action_12855395 ] 

Hudson commented on CASSANDRA-962:
----------------------------------

Integrated in Cassandra #402 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/402/])
    announce version early during startup. Patch by Gary Dusbabek, reviewed by Jonathan Ellis. CASSANDRA-962


> Schema definition propagation should happen before obtaining a bootstrap token.
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-962
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-962
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 0.7
>            Reporter: Gary Dusbabek
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: 0001-announce-version-early-during-startup.patch
>
>
> There is no reason for this not to happen.  We spend 90 seconds waiting around for load information anyway.  It would be nice to use some of that time to get the schema in place.
> CASSANDRA-785 expects this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.