[
https://issues.apache.org/jira/browse/CASSANDRA-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895037#action_12895037
]
Gary Dusbabek commented on CASSANDRA-1353:
------------------------------------------
We'd generate even more garbage if we pre-serialized the CF and them framed it
with a length field (so we could skip over the data).
One alternative I can think of is to keep and 'attic' of dropped column family
definitions in the system table so that it can be consulted in order to read
old row mutations. This is ugly though.
> commit log recovery is broken when the CL contains mutations to CFs that have
> been dropped
> ------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1353
> Project: Cassandra
> Issue Type: Bug
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Fix For: 0.7 beta 1
>
>
> This was working, so the fix should include a RecoveryManager test that
> checks for regressions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
