[jira] [Comment Edited] (CASSANDRA-10699) Make schema alterations strongly consistent

["Matt Byrd (JIRA)" <ji...@apache.org>]

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

Matt Byrd edited comment on CASSANDRA-10699 at 6/2/17 5:56 PM:
---------------------------------------------------------------

In particular I'm interested in how to avoid concurrent schema changes causing problems.
[~iamaleksey] Is the plan to use Paxos to linearise the schema changes?
btw the original assignee change was not intentional.


was (Author: mbyrd):
In particular I'm interested in how to avoid concurrent schema changes causing problems.
[~iamaleksey] Is the plan to use Paxos to linearise the schema changes?

> 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
>            Assignee: Aleksey Yeschenko
>             Fix For: 4.0
>
>
> 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.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org