[ https://issues.apache.org/jira/browse/CASSANDRA-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-9810: ---------------------------------------- Component/s: Core > Lift some counters limitations in C* 3.X > ---------------------------------------- > > Key: CASSANDRA-9810 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9810 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Aleksey Yeschenko > Priority: Major > Fix For: 4.x > > > A ticket to aggregate issues for removal of some of the counters limitations > we currently have: > 1. Counters are not reusable after deletion. It's true that deletion doesn't > commute, and an increment coming soon after a deletion would lead to > undefined behavior, but the current behavior is the result of bug in 1.1. We > should revert CASSANDRA-7346 > 2. Once that is done, we can start allowing to mix counters and non-counters > in the same tables. For read requests it means data locality, being able to > satisfy more requests with a single query. We would still be forbidding > updating counter columns and regular columns in a single {{UPDATE}}, however, > and would not allow counter updates in {{INSERT}} > See CASSANDRA-8878 for some discussion of the subject. In particular, > [this|https://issues.apache.org/jira/browse/CASSANDRA-8878?focusedCommentId=14346748&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14346748] > and > [this|https://issues.apache.org/jira/browse/CASSANDRA-8878?focusedCommentId=14351091&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14351091] > comments. > This seems to be a pre-requisite for CASSANDRA-9778. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org