cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Petracca (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10699) Make schema alterations strongly consistent
Date Tue, 17 May 2016 20:30:13 GMT

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

Tom Petracca commented on CASSANDRA-10699:
------------------------------------------

Are there any plans to be able to backport this to 2.2 or is it safe to assume that this (and
the other schema hardening issues in 9424) will only hit 3.X and beyond?

> Make schema alterations strongly consistent
> -------------------------------------------
>
>                 Key: CASSANDRA-10699
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10699
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Aleksey Yeschenko
>             Fix For: 3.x
>
>
> Schema changes do not necessarily commute. This has been the case before CASSANDRA-5202,
but now is particularly problematic.
> We should employ a strongly consistent protocol instead of relying on marshalling {{Mutation}}
objects with schema changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message