[ https://issues.apache.org/jira/browse/CASSANDRA-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561502#comment-14561502 ]
Tyler Hobbs edited comment on CASSANDRA-8502 at 5/27/15 6:56 PM: ----------------------------------------------------------------- The test results for all four branches look good. Committed as {{d075540c46209fdabde74db1e210114965372605}} to 2.0 and merged to 2.1, 2.2, and trunk. was (Author: thobbs): The test results for all for branches look good. Committed as {{d075540c46209fdabde74db1e210114965372605}} to 2.0 and merged to 2.1, 2.2, and trunk. > 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.6, 2.0.16, 2.2.0 rc1 > > Attachments: 8502-2.0-v2.txt, 8502-2.0.txt, 8502-2.1-v2.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 (v6.3.4#6332)