Jeff Jirsa commented on CASSANDRA-13717:

Welcome [~skonto] ! Next step would be to assign yourself (I've done that for 
you), and then hit 'submit patch' to mark the issue as patch available (I've 
done that for you again).

We typically ask either the contributor (you) or the reviewer (someone who will 
volunteer, hopefully soon) to push the patch to a github branch and kick off CI 
(we have it setup to use circleci for unit tests, and a committer can kick off 
dtests). We typically ask that your patch includes a test case that fails 
before your patch and succeeds after it's applied, so while this is not a 
review, I will say that any reviewer should ask you to do that. 

> 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
>         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