You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2017/08/03 13:44:03 UTC
[jira] [Resolved] (CASSANDRA-13730) Dropping a table doesn't drop
its dropped columns
[ https://issues.apache.org/jira/browse/CASSANDRA-13730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko resolved CASSANDRA-13730.
-------------------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.11.x)
(was: 3.0.x)
3.11.1
3.0.15
> Dropping a table doesn't drop its dropped columns
> -------------------------------------------------
>
> Key: CASSANDRA-13730
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13730
> Project: Cassandra
> Issue Type: Bug
> Components: Distributed Metadata
> Reporter: Duarte Nunes
> Assignee: ZhaoYang
> Priority: Minor
> Fix For: 3.0.15, 3.11.1
>
>
> I'm not sure if this is intended or not, but currently a table's dropped columns are not dropped when the table itself is dropped:
> {noformat}
> cqlsh> create keyspace ks WITH replication={ 'class' : 'SimpleStrategy', 'replication_factor' : 1 } ;
> cqlsh> use ks;
> cqlsh:ks> create table test (pk text primary key, c1 int);
> cqlsh:ks> alter table test drop c1;
> cqlsh:ks> drop table test;
> cqlsh:ks> select * from system_schema.dropped_columns where keyspace_name = 'ks' and table_name = 'test';
> keyspace_name | table_name | column_name | dropped_time | kind | type
> ---------------+------------+-------------+---------------------------------+---------+------
> ks | test | c1 | 2017-07-25 17:53:47.651000+0000 | regular | int
> (1 rows)
> {noformat}
> This can have surprising consequences when creating another table with the same name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org