[jira] [Updated] (CASSANDRA-14838) Dropped columns can cause reverse sstable iteration to return prematurely
[ https://issues.apache.org/jira/browse/CASSANDRA-14838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] C. Scott Andreas updated CASSANDRA-14838: - Severity: Critical (was: Normal) Complexity: Challenging Discovered By: Fuzz Test Bug Category: Parent values: Correctness(12982)Level 1 values: Response Corruption / Loss(12987) Since Version: 3.0.0 Component/s: (was: Legacy/Local Write-Read Paths) Local/SSTable > 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 > Components: Local/SSTable >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Urgent > 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.14#76016) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14838) Dropped columns can cause reverse sstable iteration to return prematurely
[ https://issues.apache.org/jira/browse/CASSANDRA-14838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] C. Scott Andreas updated CASSANDRA-14838: - Component/s: Local Write-Read Paths > 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 > Components: Local Write-Read Paths >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
[jira] [Updated] (CASSANDRA-14838) Dropped columns can cause reverse sstable iteration to return prematurely
[ https://issues.apache.org/jira/browse/CASSANDRA-14838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-14838: Resolution: Fixed Status: Resolved (was: Ready to Commit) committed as e4bac44a04d59d93f622d91ef40b462250dac613, thanks > 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
[jira] [Updated] (CASSANDRA-14838) Dropped columns can cause reverse sstable iteration to return prematurely
[ https://issues.apache.org/jira/browse/CASSANDRA-14838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-14838: Status: Ready to Commit (was: Patch Available) > 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
[jira] [Updated] (CASSANDRA-14838) Dropped columns can cause reverse sstable iteration to return prematurely
[ 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
