You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2014/12/17 17:46:14 UTC
[jira] [Commented] (CASSANDRA-8502) Static columns returning null
for pages after first
[ https://issues.apache.org/jira/browse/CASSANDRA-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250100#comment-14250100 ]
Sylvain Lebresne commented on CASSANDRA-8502:
---------------------------------------------
It's actually pretty easy to explain, as if we page in the middle of a partition, we'll start reading in the middle of said partition and thus miss the static data. I guess we'll have to detect if there is static columns to be fetched and include back a slice for the static block when we restart paging. A tad hairy but doable.
> Static columns returning null for pages after first
> ---------------------------------------------------
>
> Key: CASSANDRA-8502
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8502
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Flavien Charlon
> Attachments: null-static-column.txt
>
>
> When paging is used for a query containing a static column, the first page contains the right value for the static column, but subsequent pages have null null for the static column instead of the expected value.
> Repro steps:
> - Create a table with a static column
> - Create a partition with 500 cells
> - Using cqlsh, query that partition
> Actual result:
> - You will see that first, the static column appears as expected, but if you press a key after "---MORE---", the static columns will appear as null.
> See the attached file for a repro of the output.
> I am using a single node cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)