[
https://issues.apache.org/jira/browse/CASSANDRA-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-16944:
---------------------------------------
Test and Documentation Plan: The patches add new unit tests and distributed
tests. It also update existing unit tests.
Status: Patch Available (was: In Progress)
|| Branche || CI ||
| [3.0|https://github.com/apache/cassandra/pull/1200] |
[j8|https://app.circleci.com/pipelines/github/blerer/cassandra?branch=CASSANDRA-16944-3.0]
|
| [3.11|https://github.com/apache/cassandra/pull/1198] |
[j8|https://app.circleci.com/pipelines/github/blerer/cassandra/207/workflows/cc17987b-b70f-433b-b005-3a9bb2705363]
|
| [4.0|https://github.com/apache/cassandra/pull/1199]
|[j8|https://app.circleci.com/pipelines/github/blerer/cassandra/208/workflows/c2224be7-d0ab-4b4a-af9e-48c25cb1849b],
[j11|https://app.circleci.com/pipelines/github/blerer/cassandra/208/workflows/d3a6c41c-152f-4a4b-8327-7ffe7e12e71e]
|
The 3.0 patch unit tests slightly differ from the other branches as the 3.0
require the static columns to always be read even if they are not queried.
The 4.0 patch logic handle range deletion in a different way than the other
branches due to CASSANDRA-15369 that modified the logic in the 4.0 branch.
> 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.x, 3.11.x, 4.0.x
>
>
> 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]
