[
https://issues.apache.org/jira/browse/CASSANDRA-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162134#comment-16162134
]
Jason Brown commented on CASSANDRA-13717:
-----------------------------------------
This bug exists in 3.0, as well - perhaps earlier, but even if it does this
doesn't meet the bar of being 'critical' to patch 2.x for.
> INSERT statement fails when Tuple type is used as clustering column with
> default DESC order
> -------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-13717
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13717
> Project: Cassandra
> Issue Type: Bug
> Components: Core, CQL
> Environment: Cassandra 3.11
> Reporter: Anastasios Kichidis
> Assignee: Stavros Kontopoulos
> Priority: Critical
> Fix For: 3.0.x, 3.11.x, 4.x
>
> Attachments: example_queries.cql, fix_13717
>
>
> 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)
> {noformat}
> create table test_table (
> id int,
> tdemo tuple<timestamp, varchar>,
> primary key (id, tdemo)
> ) with clustering order by (tdemo desc);
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
