[CASSANDRA-9810] Lift some counters limitations in C* 3.X

• Type: Improvement
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 5.x
• Component/s: Legacy/Core
• Assignee: Unassigned Assign to me
• Reporter: Aleksey Yeschenko
• Created: 14/Jul/15 22:49
• Updated: 07/Mar/23 10:53

Description

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 and this comments.

This seems to be a pre-requisite for CASSANDRA-9778.

Issue Links

• is duplicated by: CASSANDRA-8878 Counter Tables should be more clearly identified
• is required by: CASSANDRA-9778 CQL support for time series aggregation
• relates to: CASSANDRA-7346 Modify reconcile logic to always pick a tombstone over a counter cell
• relates to: CASSANDRA-8878 Counter Tables should be more clearly identified