[
https://issues.apache.org/jira/browse/CASSANDRA-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-16944:
---------------------------------------
Fix Version/s: (was: 4.0.x)
(was: 3.11.x)
(was: 3.0.x)
4.0.2
3.11.12
3.0.26
Since Version: 3.0.0
Source Control Link:
https://github.com/apache/cassandra/commit/9f492844d5401d4d856c3bf5b908ba84d1b92a0c
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed into 3.0 at 9f492844d5401d4d856c3bf5b908ba84d1b92a0c and merged into
3.11, 4.0 and trunk
> Single partition reads can read more SSTables than required
> ------------------------------------------------------------
>
> Key: CASSANDRA-16944
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16944
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Benjamin Lerer
> Assignee: Benjamin Lerer
> Priority: Normal
> Fix For: 3.0.26, 3.11.12, 4.0.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> For some scenarios involving row deletions, range deletions or static
> columns, the logic of
> {{SinglePartitionReadCommand.queryMemtableAndSSTablesInTimestampOrder}} might
> trigger more SSTables reads that expected.
> For row deletions and range deletions the reasons is that the logic do not
> take them into account. Once we hit a deleted row (caused by a row deletion
> or a range deletion) with a timestamp higher than the one of the next SStable
> we know that we can stop reading more SSTables.
> For static columns the problems seems to have been introduced by the changes
> in CASSANDRA-16671.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
