cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8502) Static columns returning null for pages after first
Date Tue, 03 Feb 2015 23:59:36 GMT


Tyler Hobbs commented on CASSANDRA-8502:

bq. I don't think this handle range queries (for the reversed case) \[...\]

We don't allow {{ORDER BY}} unless you restrict the partition key with EQ or IN, so we should
be good there, unless I'm missing something.

I should be able to respond to or address the other comments tomorrow, thanks.

> Static columns returning null for pages after first
> ---------------------------------------------------
>                 Key: CASSANDRA-8502
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Flavien Charlon
>            Assignee: Tyler Hobbs
>             Fix For: 2.1.3, 2.0.13
>         Attachments: 8502-2.0.txt, 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

View raw message