[
https://issues.apache.org/jira/browse/CASSANDRA-6532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048710#comment-14048710
]
Aleksey Yeschenko commented on CASSANDRA-6532:
----------------------------------------------
Same thing, same reason, same reasoning. A range tombstone instead of a
partition tombstone in this case. Basically, if you do delete counters, delete
them with as high granularity as possible, if you plan to use the same
partition or the same row in the future. Until the tombstone is gone
(partition, row, or cell-level), any affected counters can't be reused.
See CASSANDRA-7346.
> Deleting and re-adding counter causes null count value.
> -------------------------------------------------------
>
> Key: CASSANDRA-6532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6532
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: cqlsh 4.1.0 | Cassandra 2.0.3 | CQL spec 3.1.1 | Thrift
> protocol 19.38.0
> Reporter: Gregory Ramsperger
> Labels: counters
>
> After a specific counter has been deleted, recreating a new counter with the
> same key causes the value to be permanently null.
> {noformat}
> cqlsh:demo> create table DemoCounter ( pk text primary key, cnt counter );
> cqlsh:demo> update DemoCounter set cnt = cnt + 1 where pk = 'foo';
> cqlsh:demo> select * from DemoCounter;
> pk | cnt
> -----+-----
> foo | 1
> (1 rows)
> cqlsh:demo> delete from DemoCounter where pk = 'foo';
> cqlsh:demo> select * from DemoCounter;
> (0 rows)
> cqlsh:demo> update DemoCounter set cnt = cnt + 1 where pk = 'foo';
> cqlsh:demo> select * from DemoCounter;
> pk | cnt
> -----+------
> foo | null
> (1 rows)
> cqlsh:demo>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
