[jira] [Commented] (CASSANDRA-8502) Static columns returning null for pages after first

["Tyler Hobbs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277974#comment-14277974 ] 

Tyler Hobbs commented on CASSANDRA-8502:
----------------------------------------

I've got a working patch for forward slices, but reversed slices are more problematic.  We need to add an extra slice over the statics for every page, but with reversed queries, the static slice comes _after_ the normal slice, so the page limit prevents the static slice from being used until the last page.  So instead of adding a second slice to the read, it looks like we'll need to split the reversed queries into two separate reads: one for the static columns, and one for the normal data.

> 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
>            Assignee: Tyler Hobbs
>             Fix For: 2.1.3, 2.0.13
>
>         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)