[
https://issues.apache.org/jira/browse/CASSANDRA-7831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110761#comment-14110761
]
Philip Thompson commented on CASSANDRA-7831:
--------------------------------------------
This does not reproduce on 2.1-HEAD. Instead what happens after
{code}
update counter_bug set c = c +1 where t = 1;
update counter_bug set c = c +1 where t = 2;
select * from counter_bug;
{code}
is that
t | c
---+---
1 | 2
2 | 1
is returned, implying that the previous value for c was preserved even though
the column was dropped.
> recreating a counter column after dropping it leaves in unusable state
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-7831
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7831
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Peter Mädel
>
> create table counter_bug (t int, c counter, primary key (t));
> update counter_bug set c = c +1 where t = 1;
> select * from counter_bug ;
>
> t | c
> ---+---
> 1 | 1
>
> (1 rows)
>
> alter table counter_bug drop c;
> alter table counter_bug add c counter;
> update counter_bug set c = c +1 where t = 1;
> select * from counter_bug;
>
> (0 rows)
> update counter_bug set c = c +1 where t = 2;
> select * from counter_bug;
>
> (0 rows)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
