[CASSANDRA-13717] INSERT statement fails when Tuple type is used as clustering column with default DESC order

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 3.0.15, 3.11.1, 4.0-alpha1, 4.0
• Component/s: Legacy/Core, Legacy/CQL

Environment

Cassandra 3.11

• Severity: Critical
• Assignee: Stavros Kontopoulos
• Reporter: Anastasios Kichidis

Authors

Stavros Kontopoulos

Reviewers

Jason Brown

• Created: 21/Jul/17 13:28
• Updated: 15/May/20 08:04
• Resolved: 12/Sep/17 21:19

Description

When a column family is created and a Tuple is used on clustering column with default clustering order DESC, then the INSERT statement fails.

For example, the following table will make the INSERT statement fail with error message "Invalid tuple type literal for tdemo of type frozen<tuple<timestamp, text>>" , although the INSERT statement is correct (works as expected when the default order is ASC)

create table test_table (
	id int,
	tdemo tuple<timestamp, varchar>,
	primary key (id, tdemo)
) with clustering order by (tdemo desc);