You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2012/09/19 10:45:07 UTC

[jira] [Updated] (CASSANDRA-4684) Binary protocol: inform clients of schema changes

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

Sylvain Lebresne updated CASSANDRA-4684:
----------------------------------------

    Attachment: 0002-Add-migration-events.txt
                0001-Return-schema-change-infos.txt

Attaching 2 patches that adds the 2 "features" described above. Note that this only affect the binary protocol, and it's relatively minor changes, so I think it's probably fine to push in beta2.

                
> Binary protocol: inform clients of schema changes
> -------------------------------------------------
>
>                 Key: CASSANDRA-4684
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4684
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.2.0 beta 2
>
>         Attachments: 0001-Return-schema-change-infos.txt, 0002-Add-migration-events.txt
>
>
> It would be nice to inform clients when a schema change occurs as this would allow said client to maintain the current state of the schema, which might be useful/desirable. To allow that, we can:
> # return that a query has changed the schema (instead of simply a 'void' return), in the same spirit than CASSANDRA-3707.
> # add events notification on schema change.
> Just to be clear, the goal is only to inform that a change has occured, the client would still have to query the system table to know the exact content of the change, but at least it'll know when to do such query.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira