[
https://issues.apache.org/jira/browse/CASSANDRA-13730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106299#comment-16106299
]
ZhaoYang edited comment on CASSANDRA-13730 at 7/30/17 4:57 AM:
---------------------------------------------------------------
This might affect backup/restore..
1. backup
2. drop column
3. drop table
4. restore schema
5. restore sstable
6. data missing for dropped column
was (Author: jasonstack):
This might affect backup/restore..
> 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
> Reporter: Duarte Nunes
> Fix For: 3.0.x, 3.11.x
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
