Sylvain Lebresne created CASSANDRA-13341:
--------------------------------------------
Summary: Legacy deserializer can create empty range tombstones
Key: CASSANDRA-13341
URL: https://issues.apache.org/jira/browse/CASSANDRA-13341
Project: Cassandra
Issue Type: Bug
Reporter: Sylvain Lebresne
Assignee: Sylvain Lebresne
Fix For: 3.0.x, 3.11.x
Range tombstones in the 2.x file format is a bit far-westy so you can actually
get sequences of range tombstones like {{\[1, 4\]@3 \[1, 10\]@5}}. But the
current legacy deserializer doesn't handle this correctly. On the first range,
it will generate a {{INCL_START(1)@3}} open marker, but upon seeing the next
tombstone it will decide to close the previously opened range and re-open with
deletion time 5, so will generate {{EXCL_END_INCL_START(1)@3-5}}. That result
in the first range being empty, which break future assertions in the code.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
