You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sumanth Pasupuleti (JIRA)" <ji...@apache.org> on 2019/07/09 13:50:00 UTC
[jira] [Commented] (CASSANDRA-10699) Make schema alterations
strongly consistent
[ https://issues.apache.org/jira/browse/CASSANDRA-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881237#comment-16881237 ]
Sumanth Pasupuleti commented on CASSANDRA-10699:
------------------------------------------------
[~iamaleksey] could you please update on what the latest status of this ticket is.
> Make schema alterations strongly consistent
> -------------------------------------------
>
> Key: CASSANDRA-10699
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10699
> Project: Cassandra
> Issue Type: Sub-task
> Components: Legacy/Distributed Metadata
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Normal
> Fix For: 4.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org