[jira] [Updated] (CASSANDRA-9179) Unable to "point in time" restore if table/cf has been recreated

["Joshua McKenzie (JIRA)" <ji...@apache.org>]

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

Joshua McKenzie updated CASSANDRA-9179:
---------------------------------------
    Component/s: CQL

> 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
>          Components: CQL
>            Reporter: Jon Moses
>            Assignee: Branimir Lambov
>              Labels: doc-impacting
>
> 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)