[
https://issues.apache.org/jira/browse/CASSANDRA-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430643#comment-13430643
]
Pavel Yaskevich commented on CASSANDRA-4487:
--------------------------------------------
The thing I don't understand is how it's different for CQL3 comparing to
Thrift/CQL, in either case if we to remove the check users won't be able to run
any operations safely except to the localhost...
> 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
