[ https://issues.apache.org/jira/browse/CASSANDRA-6505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866832#comment-13866832 ]
Aleksey Yeschenko commented on CASSANDRA-6505: ---------------------------------------------- Pushed https://github.com/iamaleksey/cassandra/commits/6505-v2, with the nits addressed and lots of (unnecessary) changes reverted. You should be sleeping better with this version. For the record - the changes in the original 6505 are there b/c I took the code more or less directly from the 6504 branch. And it was created before CASSANDRA-6506 was in plans, so if we were going to keep CounterContext, I wanted it to at least be decently rewritten. > counters++ global shards 2.0 back port > -------------------------------------- > > Key: CASSANDRA-6505 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6505 > Project: Cassandra > Issue Type: Improvement > Reporter: Aleksey Yeschenko > Assignee: Aleksey Yeschenko > Fix For: 2.0.5 > > > CASSANDRA-6504 introduces a new type of shard - 'global' - to 2.1. To enable > live upgrade from 2.0 to 2.1, it's necessary that 2.0 nodes are able to > understand the new 'global' shards in the counter contexts. > 2.0 nodes will not produce 'global' shards, but must contain the merge logic. > It isn't a trivial code change ("non-trivial code in a non-trivial part of > the code"), hence this separate JIRA issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160)