[
https://issues.apache.org/jira/browse/CASSANDRA-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430614#comment-13430614
]
Sylvain Lebresne commented on CASSANDRA-4487:
---------------------------------------------
We might also want to keep the validateSchemaIsSettled for the thrift side,
otherwise we're changing the semantic of the operation. I mean, it's fine for
CQL3, but if we really want to be conservative on the thrift side ....
(typically waiting on validateSchemaIsSettled means that you know you can start
inserting data in your newly created CF).
> 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
