You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2017/02/15 13:57:42 UTC
[jira] [Updated] (CASSANDRA-13222) Paging with reverse queries and
static columns may return incorrectly sized pages
[ https://issues.apache.org/jira/browse/CASSANDRA-13222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe updated CASSANDRA-13222:
----------------------------------------
Description: There are 2 specialisations of {{ColumnCounter}} that deal with static columns differently depending on the order of iteration through the column family and which impl is used generally depends on whether or not the {{ColumnFilter}} in use is reversed. However, the base method {{ColumnCounter::countAll}} always uses forward iteration, which can result in overcounting when the query is reversed and there are statics involved. In turn, this leads to incorrectly sized pages being returned to the client. (was: There are 2 specialisations of `ColumnCounter` that deal with static columns differently depending on the order of iteration through the column family and which impl is used generally depends on whether or not the `ColumnFilter` in use is reversed. However, the base method `ColumnCounter::countAll`` always uses forward iteration, which can result in overcounting when the query is reversed and there are statics involved. In turn, this leads to incorrectly sized pages being returned to the client.)
> Paging with reverse queries and static columns may return incorrectly sized pages
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-13222
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13222
> Project: Cassandra
> Issue Type: Bug
> Components: CQL, Local Write-Read Paths
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
>
> There are 2 specialisations of {{ColumnCounter}} that deal with static columns differently depending on the order of iteration through the column family and which impl is used generally depends on whether or not the {{ColumnFilter}} in use is reversed. However, the base method {{ColumnCounter::countAll}} always uses forward iteration, which can result in overcounting when the query is reversed and there are statics involved. In turn, this leads to incorrectly sized pages being returned to the client.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)