You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2017/08/10 01:51:00 UTC
[jira] [Updated] (CASSANDRA-13717) INSERT statement fails when
Tuple type is used as clustering column with default DESC order
[ https://issues.apache.org/jira/browse/CASSANDRA-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Jirsa updated CASSANDRA-13717:
-----------------------------------
Status: Patch Available (was: Open)
> 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
>
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org