[CASSANDRA-16686] Queries returning static content when the partition has no rows might fail to return some rows

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-rc2, 4.0
• Component/s: CQL/Interpreter
• Bug Category: Correctness - Transient Incorrect Response
• Severity: Normal
• Complexity: Normal
• Discovered By: Code Inspection
• Platform: All
• Since Version: 4.0-alpha1

Source Control Link

https://github.com/apache/cassandra/commit/2059c7586ef6bf10900977d4f5bb1072313e0b74

Test and Documentation Plan

The patch add multiple unit tests

• Assignee: Benjamin Lerer
• Reporter: Benjamin Lerer

Authors

Benjamin Lerer

Reviewers

Andres de la Peña, Jacek Lewandowski

• Created: 21/May/21 10:00
• Updated: 14/Jun/21 07:35
• Resolved: 10/Jun/21 09:18

Description

The problem can be reproduced with the following test:

    @Test
    public void testStaticColumnDeletionWithMultipleStaticColumns() throws Throwable
    {
        createTable("CREATE TABLE %s (pk int, ck int, s1 int static, s2 int static, v int, PRIMARY KEY(pk, ck))");
        execute("INSERT INTO %s (pk, s1, s2) VALUES (1, 1, 1) USING TIMESTAMP 1000");
        flush();
        execute("INSERT INTO %s (pk, s1) VALUES (1, 2) USING TIMESTAMP 2000");
        flush();
        execute("DELETE s1 FROM %s USING TIMESTAMP 3000 WHERE pk = 1");
        flush();
        assertRows(execute("SELECT * FROM %s WHERE pk=1"), row(1, null, null, 1, null));
        assertRows(execute("SELECT s1, s2 FROM %s WHERE pk=1"), row((Integer) null, 1));
        assertRows(execute("SELECT s1 FROM %s WHERE pk=1"), row((Integer) null)); // <-FAIL
    }

This problem is a regression in 4.0 and trunk

Issue Links

• is related to: CASSANDRA-16671 Cassandra can return no row when the row columns have been deleted.