cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Moses (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9179) Unable to "point in time" restore if table/cf has been recreated
Date Mon, 13 Apr 2015 15:13:12 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jon Moses updated CASSANDRA-9179:
---------------------------------
    Description: 
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.

  was:
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 keyspace has been dropped
and recreated.

When the keyspace 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.

        Summary: Unable to "point in time" restore if table/cf has been recreated  (was: Unable
to "point in time" restore if keyspace has been created)

> 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
>
> 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)

Mime
View raw message