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

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1.13, 2.2.5, 3.0.3, 3.2
• Component/s: Legacy/CQL, Legacy/Distributed Metadata
• Labels: doc-impacting
• Severity: Normal
• Assignee: Branimir Lambov
• Reporter: Jon Moses

Authors

Branimir Lambov

Reviewers

Marcus Eriksson

• Created: 13/Apr/15 15:08
• Updated: 16/Apr/19 09:31
• Resolved: 15/Dec/15 09:31

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.

Issue Links

• relates to: CASSANDRA-5202 CFs should have globally and temporally unique CF IDs to prevent "reusing" data from earlier incarnation of same CF name