cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-14008) RTs at index boundaries in 2.x sstables can create unexpected CQL row in 3.x
Date Sun, 12 Nov 2017 21:27:02 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-14008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248993#comment-16248993
] 

Jeff Jirsa commented on CASSANDRA-14008:
----------------------------------------

It does create an invalid (or similarly broken)  sstable on compaction/upgradesstables, and
while I've got a fix for the original problem done, I need to think about the right way to
un-break the resulting 3.0 sstable (which should be do-able, based on what I've seen so far).






> RTs at index boundaries in 2.x sstables can create unexpected CQL row in 3.x
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14008
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14008
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jeff Jirsa
>            Assignee: Jeff Jirsa
>              Labels: correctness
>             Fix For: 3.0.x, 3.11.x
>
>
> In 2.1/2.2, it is possible for a range tombstone that isn't a row deletion and isn't
a complex deletion to appear between two cells with the same clustering. The 8099 legacy code
incorrectly treats the two (non-RT) cells as two distinct CQL rows, despite having the same
clustering prefix.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message