[
https://issues.apache.org/jira/browse/CASSANDRA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627265#comment-13627265
]
Aleksey Yeschenko commented on CASSANDRA-3919:
----------------------------------------------
K, I think I see how "Why do we only call discardDropped if it has re-added
columns?" is valid. The other thing is most likely wrong, though.
Will push a new, trunk-based, branch tomorrow.
> 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: 2.0
>
>
> 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
