[
https://issues.apache.org/jira/browse/CASSANDRA-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055708#comment-15055708
]
Marcus Eriksson edited comment on CASSANDRA-9179 at 12/14/15 9:45 AM:
----------------------------------------------------------------------
in general, +1 on the patches
The 2.2 patch seems to be based on 2.1, should this go into 2.2+?
nits:
* on the 2.1/2.2 patch, whitespace on line 88 in CFPropDefs
* in 3.0, should the KW_ID go into TableParams.Option ?
was (Author: krummas):
+1 on the patches
The 2.2 patch seems to be based on 2.1, should this go into 2.2+?
and a small nit on the 2.1/2.2 patch, whitespace on line 88 in CFPropDefs
> 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)
