[CASSANDRA-15906] Queries on KEYS 2i are broken by DROP COMPACT STORAGE on 3.0

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.21, 3.11.7, 4.0-beta1, 4.0
• Component/s: CQL/Interpreter
• Bug Category: Degradation - Other Exception
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: Unit Test
• Platform: All
• Since Version: 3.0.0

Source Control Link

https://github.com/apache/cassandra/commit/64c80f4ef89f0cc88c15febed8c01eb07ae0a84e

Test and Documentation Plan

upgrade dtest included

• Assignee: Sylvain Lebresne
• Reporter: Sylvain Lebresne

Authors

Sylvain Lebresne

Reviewers

Brandon Williams

• Created: 29/Jun/20 15:14
• Updated: 03/Jan/21 17:03
• Resolved: 23/Jul/20 23:19

Description

From 3.0 onwards, the declared columns of a thrift table are internally static columns. While the table is compact, this

After DROP COMPACT STORAGE is used on a table that has a KEYS 2i, queries that uses that index will start failing with:

Queries using 2ndary indexes don't support selecting only static columns

In 3.0, we don't support index on static columns and have that validation that rejects 2i queries on static columns. But the declared columns of compact table are static under the hood, and while this specific validation is skipped while the table is compact, it isn't anymore after the DROP COMPACT STORAGE.

Note that internally, nothing changes with the DROP COMPACT STORAGE, and the 2i queries would still work as well as before, it is just that they are rejected.

Also not that this is only a problem in 3.0. In 3.11, static column indexes were added (CASSANDRA-8103) and thus this validation has been removed, and everything works as it should.

However, since DROP COMPACT STORAGE is a mandatory step for compact tables before upgrading to 4.0, fixing this annoying in 3.0 would avoid forcing users with KEYS 2i on 3.0 to upgrade to 3.11 before going to 4.0.