Please sign in to comment.
sstable: fix read failure of certain sstables
We had a problem reading certain existing Cassandra sstables into Scylla. Our consume_range_tombstone() function assumes that the start and end columns have a certain "end of component" markers, and want to verify that assumption. But because of bugs in older versions of Cassandra, see https://issues.apache.org/jira/browse/CASSANDRA-7593, sometimes the "end of component" was missing (set to 0). CASSANDRA-7593 suggested this problem might exist on the start column, so we allowed for that, but now we discovered a case where also the end column is set to 0 - causing the test in consume_range_tombstone() to fail and the sstable read to fail - causing Scylla to no be able to import that sstable from Cassandra. Allowing for an 0 also on the end column made it possible to read that sstable, compact it, and so on. Fixes #1125. Signed-off-by: Nadav Har'El <firstname.lastname@example.org> Message-Id: <email@example.com> (cherry picked from commit a05577c)
- Loading branch information...