[jira] [Assigned] (CASSANDRA-10699) Make schema alterations strongly consistent
[ https://issues.apache.org/jira/browse/CASSANDRA-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd reassigned CASSANDRA-10699: - Assignee: Aleksey Yeschenko (was: Matt Byrd) > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-10699) Make schema alterations strongly consistent
[ https://issues.apache.org/jira/browse/CASSANDRA-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd reassigned CASSANDRA-10699: - Assignee: Matt Byrd > 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: Matt Byrd > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org