You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Mike Bulman (JIRA)" <ji...@apache.org> on 2015/04/14 17:28:13 UTC
[jira] [Commented] (CASSANDRA-9179) Unable to "point in time"
restore if table/cf has been recreated
[ https://issues.apache.org/jira/browse/CASSANDRA-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494255#comment-14494255 ]
Mike Bulman commented on CASSANDRA-9179:
----------------------------------------
Two things to add:
* This also applies to the case where a schema has been changed but then reverted, leaving you with an identical and compatible schema, but a separate table id and no ability to replay commitlogs
* auto snapshot does not help if you want to restore to a point in time prior to the drop
> Unable to "point in time" restore if table/cf has been recreated
> ----------------------------------------------------------------
>
> Key: CASSANDRA-9179
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9179
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jon Moses
> Assignee: Branimir Lambov
>
> With Cassandra 2.1, and the addition of the CF UUID, the ability to do a "point in time" restore by restoring a snapshot and replaying commitlogs is lost if the table has been dropped and recreated.
> When the table is recreated, the cf_id changes, and the commitlog replay mechanism skips the desired mutations as the cf_id no longer matches what's present in the schema.
> There should exist a way to inform the replay that you want the mutations replayed even if the cf_id doesn't match.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)