[
https://issues.apache.org/jira/browse/CASSANDRA-14838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-14838:
----------------------------------------
Reviewer: Sam Tunnicliffe
Status: Patch Available (was: Open)
|[3.0|https://github.com/bdeggleston/cassandra/tree/14838-3.0]|[circle|https://circleci.com/gh/bdeggleston/workflows/cassandra/tree/cci%2F14838-3.0]|
|[3.11|https://github.com/bdeggleston/cassandra/tree/14838-3.11]|[circle|https://circleci.com/gh/bdeggleston/workflows/cassandra/tree/cci%2F14838-3.11]|
|[trunk|https://github.com/bdeggleston/cassandra/tree/14838-trunk]|[circle|https://circleci.com/gh/bdeggleston/workflows/cassandra/tree/cci%2F14838-trunk]|
> Dropped columns can cause reverse sstable iteration to return prematurely
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-14838
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14838
> Project: Cassandra
> Issue Type: Bug
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Priority: Major
> Fix For: 3.0.18, 3.11.4, 4.0
>
>
> CASSANDRA-14803 fixed an issue where reading legacy sstables in reverse could
> return early in certain cases. It's also possible to get into this state with
> current version sstables if there are 2 or more indexed blocks in a row that
> only contain data for a dropped column. Post 14803, this will throw an
> exception instead of returning an incomplete response, but it should just
> continue reading like it does for legacy sstables
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
