[
https://issues.apache.org/jira/browse/CASSANDRA-7831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112289#comment-14112289
]
Jonathan Ellis commented on CASSANDRA-7831:
-------------------------------------------
bq. until maybe we push dropped columns machinery deeper in the storage engine,
I suggest simply rejecting ALTER TABLE ADD if a counter column with this name
had been dropped in the past.
We don't track dropped columns explicitly anywhere, do we? Is adding that
really so much simpler than fixing it?
> 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)
