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] [Resolved] (CASSANDRA-14008) RTs at index boundaries in 2.x sstables can create unexpected CQL row in 3.x
Date Tue, 12 Dec 2017 18:01:01 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-14008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeff Jirsa resolved CASSANDRA-14008.
------------------------------------
    Resolution: Fixed

Thanks Aleksey. Committed as {{4a2b516a3488ab04ee3338e74397b8c6d69e6d43}}

> 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: Local Write-Read Paths
>            Reporter: Jeff Jirsa
>            Assignee: Jeff Jirsa
>              Labels: correctness
>             Fix For: 3.0.16, 3.11.2
>
>
> 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