[
https://issues.apache.org/jira/browse/CASSANDRA-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055844#comment-15055844
]
Branimir Lambov commented on CASSANDRA-9179:
--------------------------------------------
bq. in 3.0, should the KW_ID go into TableParams.Option
Not sure. I did not want to put it in the {{TableParams}} as they can be
changed using {{CFMetaData.params}}. If it's not a {{TableParams}} value I
didn't think it's a good idea to put the identifier (and validation etc.) there.
I targeted 2.2, but it looks like the patch is fine on 2.1 as well. Uploaded a
2.1 branch with the whitespace removed:
|[2.1/2.2
code|https://github.com/blambov/cassandra/tree/9179-with-id-2.1]|[utests|http://cassci.datastax.com/view/Dev/view/blambov/job/blambov-9179-with-id-2.1-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/blambov/job/blambov-9179-with-id-2.1-dtest/]|
> 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, Distributed Metadata
> 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)
