[CASSANDRA-8502] Static columns returning null for pages after first

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.0.16, 2.1.6, 2.2.0 rc1
• Severity: Normal
• Assignee: Tom Hobbs
• Reporter: Flavien Charlon

Authors

Tom Hobbs

Reviewers

Sylvain Lebresne

• Created: 17/Dec/14 16:28
• Updated: 16/Apr/19 09:31
• Resolved: 28/May/15 15:41

Description

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.

Issue Links

• is duplicated by: CASSANDRA-8203 Unexpected null static column
• is duplicated by: CASSANDRA-8824 cassandra python driver return None when querying static column on partition bigger than 5000 entites
• is duplicated by: CASSANDRA-8823 When listed in cqlsh static column has value only for first 100 records.