cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10699) Make schema alterations strongly consistent
Date Wed, 25 Apr 2018 11:16:00 GMT

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

Aleksey Yeschenko commented on CASSANDRA-10699:
-----------------------------------------------

bq. With this change, will schema alterations be versioned? I think this would be helpful
when plugging in other storage engines.

Yes, keyspace-scoped.

> 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
>            Priority: Major
>             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
(v7.6.3#76005)

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


Mime
View raw message