[jira] [Comment Edited] (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:comment-tabpanel=16121536#comment-16121536 ] Stavros Kontopoulos edited comment on CASSANDRA-13717 at 8/10/17 12:29 PM: --- [~jjirsa] I added a test there in TupleTypeTest, updated the branch. How can I update the patch? Should I cancel it and add a new one? was (Author: skonto): I added a test there in TupleTypeTest, updated the branch. > 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>" , although the INSERT statement is correct > (works as expected when the default order is ASC) > {noformat} > create table test_table ( > id int, > tdemo tuple , > 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
[jira] [Comment Edited] (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:comment-tabpanel=16121472#comment-16121472 ] Stavros Kontopoulos edited comment on CASSANDRA-13717 at 8/10/17 11:14 AM: --- [~jjirsa] I fixed it for trunk (version 4). I could backport it to 3.11 (version reported) as soon as it is verified that this fix is ok. Good to know about the test procedure, thanx a lot! I will check the unit tests. was (Author: skonto): [~jjirsa] I fixed it for trunk (version 4). I could backport it to 3.11 (version reported) as soon as it is verified that this fix is ok. Good to know about the test procedure thanx a lot. I will check the unit tests. > 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>" , although the INSERT statement is correct > (works as expected when the default order is ASC) > {noformat} > create table test_table ( > id int, > tdemo tuple , > 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
[jira] [Comment Edited] (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:comment-tabpanel=16121472#comment-16121472 ] Stavros Kontopoulos edited comment on CASSANDRA-13717 at 8/10/17 11:13 AM: --- [~jjirsa] I fixed it for trunk (version 4). I could backport it to 3.11 (version reported) as soon as it is verified that this fix is ok. Good to know about the test procedure thanx a lot. I will check the unit tests. was (Author: skonto): [~jjirsa] I fixed for trunk (version 4). I could backport it to 3.11 (version reported) as soon as it is verified that this fix is ok. Good to know about the test procedure thanx a lot. I will check the unit tests. > 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>" , although the INSERT statement is correct > (works as expected when the default order is ASC) > {noformat} > create table test_table ( > id int, > tdemo tuple , > 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
[jira] [Comment Edited] (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:comment-tabpanel=16120927#comment-16120927 ] Stavros Kontopoulos edited comment on CASSANDRA-13717 at 8/10/17 1:47 AM: -- I have created a patch and verified Jeff's suggestion: [patch|https://drive.google.com/open?id=0B0SeiqgJaLZvclhmY0N4dEJtUGs] {noformat} cqlsh> create keyspace test with replication = {'class':'SimpleStrategy','replication_factor': 1};cqlsh> create table test.test_table ( id int, tdemo tuple, primary key (id, tdemo) ) with clustering order by (tdemo desc); cqlsh> insert into test.test_table (id, tdemo) values (1, ('2017-02-03 03:05+','Europe')); cqlsh> select * from test.test_table; id | tdemo +--- 1 | ('2017-02-03 03:05:00.00+', 'Europe') (1 rows) {noformat} What are the next steps for the review (I am new here)? was (Author: skonto): I have created a patch and verified Jeff's suggestion: [patch|https://drive.google.com/open?id=0B0SeiqgJaLZvclhmY0N4dEJtUGs] {noformat} cqlsh> create keyspace test with replication = {'class':'SimpleStrategy','replication_factor': 1};cqlsh> create table test.test_table ( id int, tdemo tuple , primary key (id, tdemo) ) with clustering order by (tdemo desc); cqlsh> insert into test.test_table (id, tdemo) values (1, ('2017-02-03 03:05+','Europe')); cqlsh> select * from test.test_table; id | tdemo +--- 1 | ('2017-02-03 03:05:00.00+', 'Europe') (1 rows) {noformat} > 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 > 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 >" , although the INSERT statement is correct > (works as expected when the default order is ASC) > {noformat} > create table test_table ( > id int, > tdemo tuple , > 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
[jira] [Comment Edited] (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:comment-tabpanel=16120927#comment-16120927 ] Stavros Kontopoulos edited comment on CASSANDRA-13717 at 8/10/17 1:45 AM: -- I have created a patch and verified Jeff's suggestion: [patch|https://drive.google.com/open?id=0B0SeiqgJaLZvclhmY0N4dEJtUGs] {noformat} cqlsh> create keyspace test with replication = {'class':'SimpleStrategy','replication_factor': 1};cqlsh> create table test.test_table ( id int, tdemo tuple, primary key (id, tdemo) ) with clustering order by (tdemo desc); cqlsh> insert into test.test_table (id, tdemo) values (1, ('2017-02-03 03:05+','Europe')); cqlsh> select * from test.test_table; id | tdemo +--- 1 | ('2017-02-03 03:05:00.00+', 'Europe') (1 rows) {noformat} was (Author: skonto): I have created a patch and verified Jeff's suggestion: [patch|https://drive.google.com/open?id=0B0SeiqgJaLZvclhmY0N4dEJtUGs] > 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 > 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 >" , although the INSERT statement is correct > (works as expected when the default order is ASC) > {noformat} > create table test_table ( > id int, > tdemo tuple , > 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
[jira] [Comment Edited] (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:comment-tabpanel=16120927#comment-16120927 ] Stavros Kontopoulos edited comment on CASSANDRA-13717 at 8/10/17 1:44 AM: -- I have created a patch and verified Jeff's suggestion: [patch|https://drive.google.com/open?id=0B0SeiqgJaLZvclhmY0N4dEJtUGs] was (Author: skonto): I have created a patch and verified Jeff's suggestion: [patch title|https://drive.google.com/open?id=0B0SeiqgJaLZvclhmY0N4dEJtUGs] > 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 > 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>" , although the INSERT statement is correct > (works as expected when the default order is ASC) > {noformat} > create table test_table ( > id int, > tdemo tuple , > 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