Jeff Jirsa commented on CASSANDRA-13717:

[~skonto] - do you know which versions need to be fixed? 3.0? 3.11? trunk?

I've kicked off some test builds [here (unit 
tests)|https://circleci.com/gh/jeffjirsa/cassandra/tree/cassandra-13717] and 
 - we'll want to do that for each branch that needs this fix (and of course, 
we'll want to add tests to this fix as well).

> 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
>         Environment: Cassandra 3.11
>            Reporter: Anastasios Kichidis
>            Assignee: Stavros Kontopoulos
>            Priority: Critical
>         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

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to