cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1406) Dropping column families doesn't clean up secondary indexes
Date Thu, 26 Aug 2010 18:39:54 GMT


Gary Dusbabek commented on CASSANDRA-1406:

putting the deletion in Table.dropCF() is risky wrt KS and CF renames.  It won't hurt anything
right now because the delete tries to remove the old files.  If that side-effect ever went
away we'd be deleting valid files.  As it stands with this patch we'd be trying to do cleanup
of sstables that have had their files moved out from underneath them, which probably isn't
the best thing to try.

Is this a good ticket to lump in that RenameKeyspace and RenameColumnFamily don't address
secondary indices, or should that be a new one?

> Dropping column families doesn't clean up secondary indexes
> -----------------------------------------------------------
>                 Key: CASSANDRA-1406
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7 beta 1
>            Reporter: Gary Dusbabek
>            Assignee: Jonathan Ellis
>             Fix For: 0.7 beta 2
>         Attachments: 1406.txt

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message