Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 7 Aug 2012 21:33:10 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1154031902.1511.1344375190815.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <552197652.12358.1344032522661.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (CASSANDRA-4487) remove uses of
 SchemaDisagreementException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-4487:
-------------------------------------------

bq. typically waiting on validateSchemaIsSettled means that you know you can start inserting data in your newly created CF

I don't understand -- we don't do that on the normal request path even in thrift, just for schema mutations.  
                
> remove uses of SchemaDisagreementException
> ------------------------------------------
>
>                 Key: CASSANDRA-4487
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4487
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.2
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 1.2
>
>         Attachments: 0001-code-changes.patch, 0002-re-generated-thrift.patch
>
>
> Since we can handle concurrent schema changes now, there's no need to validateSchemaAgreement before modification now.

--
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