cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13525) ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade
Date Thu, 11 May 2017 14:28:04 GMT

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

Sam Tunnicliffe commented on CASSANDRA-13525:
---------------------------------------------

Fixed the 3.0 -> 3.11 merge issue, so both branches are up now, I'll update with CI results
shortly.
Trunk obviously isn't affected through removing support for pre-3.0 sstables.

||branch||circle-ci||
|[13525-3.0|https://github.com/beobal/cassandra/tree/13525-3.0]|
|[13525-3.11|https://github.com/beobal/cassandra/tree/13525-3.11]|



> ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-13525
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13525
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>
> During an upgrade from 2.1 (or 2.2) to 3.0 (or 3.x) queries which perform reverse iteration
may silently drop rows from their results. This can happen before sstableupgrade is run and
when the sstables are indexed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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


Mime
View raw message