cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3919) Dropping a column should do more than just remove the definition
Date Sat, 16 Mar 2013 04:16:13 GMT


Aleksey Yeschenko commented on CASSANDRA-3919:

- ALTER TABLE RENAME is limited to CQL3 tables (composite && !compact)
- dropped columns are stored as a map<column, dropped_time>
- the map is a json pseudomap, not a collection. let's convert everything in one go in CASSANDRA-4603
- for compaction, it seems like modifying CFS.removeDeletedStandard() alone is enough

Tested modified compaction manually before implementing extra-filtering in reads, tested reads
manually (+ collection updates that require read-before-write). Everything seems to work.

What's left:
- write dtests for reads
- write unit tests for compaction leaving out dropped columns (can't be a dtest)
- update cqlsh help
- update CQL3 doc

Will do these after the patch is committed, but before resolving the issue in jira.
> Dropping a column should do more than just remove the definition
> ----------------------------------------------------------------
>                 Key: CASSANDRA-3919
>                 URL:
>             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:

View raw message