cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3919) Dropping a column should do more than just remove the definition
Date Mon, 18 Mar 2013 08:10:16 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604931#comment-13604931
] 

Sylvain Lebresne commented on CASSANDRA-3919:
---------------------------------------------

bq. the map is a json pseudomap, not a collection. let's convert everything in one go in CASSANDRA-4603

If this ticket is going to go in 1.2 as the current fix version suggests, I'd advise not using
a json pseudomap because it is quite unclear to me that CASSANDRA-4603 won't require special
casings in the code for each property that needs to be converted. So the pseudomaps we have,
the more work/special casings we might have to do.
                
> 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

Mime
View raw message