cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-9810) Lift some counters limitations in C* 3.X
Date Fri, 23 Oct 2015 14:34:28 GMT


Aleksey Yeschenko updated CASSANDRA-9810:
    Assignee:     (was: Aleksey Yeschenko)

> Lift some counters limitations in C* 3.X
> ----------------------------------------
>                 Key: CASSANDRA-9810
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Aleksey Yeschenko
>             Fix For: 3.x
> A ticket to aggregate issues for removal of some of the counters limitations we currently
> 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|]
> This seems to be a pre-requisite for CASSANDRA-9778.

This message was sent by Atlassian JIRA

View raw message