You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Pavel Yaskevich (JIRA)" <ji...@apache.org> on 2011/06/10 14:45:59 UTC

[jira] [Updated] (CASSANDRA-2756) Make CQL CREATE KS/CF not return until the operation is complete

     [ https://issues.apache.org/jira/browse/CASSANDRA-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Yaskevich updated CASSANDRA-2756:
---------------------------------------

    Attachment: CASSANDRA-2756.patch

validates schema agreement after CREATE/UPDATE on KS/CF and CREATE/DROP index, ALTER TABLE.

> Make CQL CREATE KS/CF not return until the operation is complete
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-2756
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2756
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 0.8.0
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 0.8.1
>
>         Attachments: CASSANDRA-2756.patch
>
>
> this would be more in line with the principle of least surprise, and would avoid the need for everyone who does programmatic schema manipulation to re-invent logic like CASSANDRA-2649.
> CliClient.validateSchemaIsSettled is a good template for the logic we want.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira