[ https://issues.apache.org/jira/browse/CASSANDRA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604113#comment-13604113 ]
Jonathan Ellis commented on CASSANDRA-3919: ------------------------------------------- Does limiting RENAME mean we can't change the "columnN" defaults that upgraded < 1.2 tables would have? > Dropping a column should do more than just remove the definition > ---------------------------------------------------------------- > > Key: CASSANDRA-3919 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3919 > Project: Cassandra > Issue Type: Sub-task > Components: Core > Reporter: Jonathan Ellis > Assignee: Aleksey Yeschenko > Labels: compaction, cql > Fix For: 1.2.4 > > > Dropping a column should: > - immediately make it unavailable for {{SELECT}}, including {{SELECT *}} > - eventually (i.e., post-compaction) reclaim the space formerly used by that > column -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira