[CASSANDRA-4752] Drop keyspace causes schema disagreement

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.1.6
• Severity: Normal
• Assignee: Sam Tunnicliffe
• Reporter: Sam Tunnicliffe

Authors

Sam Tunnicliffe

Reviewers

Jonathan Ellis

• Created: 03/Oct/12 10:38
• Updated: 16/Apr/19 09:32
• Resolved: 04/Oct/12 15:29

Description

The fix for CASSANDRA-4698 introduced a bug whereby when drop keyspace is issued a schema disagreement immediately occurs. This seems to be because the

ColumnFamily cf = ColumnFamily.create(modification.getValue().metadata());

in RowMutation.deserializeFixingTimestamps does not preserve deletion info for the cf in the modification. In most cases, this doesn't cause a problem, but for a drop keyspace modification, there are no columns in the cf, so the deletion info is effectively lost leading to an incorrect digest being created and ultimately a schema disagreement.

Replacing the create with cloneMeShallow does preserve the deletion info and avoids the schema disagreement issue.