You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "paul cannon (JIRA)" <ji...@apache.org> on 2012/09/09 06:35:07 UTC
[jira] [Updated] (CASSANDRA-4362) cqlsh can't display reversed type
values properly
[ https://issues.apache.org/jira/browse/CASSANDRA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-4362:
-----------------------------------
Fix Version/s: 1.2.0
Since the python-cql driver supports parametrized types as of its 1.1 version, it is now trivial to teach it how to deal with ReversedType. I've done that in the driver, and once we get a new release into cassandra this should be fixed for cassandra 1.2.
> cqlsh can't display reversed type values properly
> -------------------------------------------------
>
> Key: CASSANDRA-4362
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4362
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 1.1.1
> Reporter: Ahmet AKYOL
> Assignee: paul cannon
> Priority: Minor
> Labels: cqlsh
> Fix For: 1.2.0
>
>
> Here is table and data:
> CREATE TABLE t1 (
> a int,
> b bigint,
> c varchar,
> d varchar,
> PRIMARY KEY (a,b,c)
> ) WITH CLUSTERING ORDER BY (b DESC, c DESC);
> INSERT INTO db.t1 (a,b,c,d) VALUES (1,10,'u1','s1');
> INSERT INTO db.t1 (a,b,c,d) VALUES (1,15,'u1','d1');
> INSERT INTO db.t1 (a,b,c,d) VALUES (1,21,'u3','ghfgh f1g');
> INSERT INTO db.t1 (a,b,c,d) VALUES (1,31,'u2','1gh');
> INSERT INTO db.t1 (a,b,c,d) VALUES (1,41,'u3','fgh1');
> And here's the query
> cqlsh:db> SELECT * FROM t1;
> a | b | c | d
> ---+----------------------------------+----+-----------
> 1 | \x00\x00\x00\x00\x00\x00\x00) | u3 | fgh1
> 1 | \x00\x00\x00\x00\x00\x00\x00\x1f | u2 | 1gh
> 1 | \x00\x00\x00\x00\x00\x00\x00\x15 | u3 | ghfgh f1g
> 1 | \x00\x00\x00\x00\x00\x00\x00\x0f | u1 | d1
> 1 | \x00\x00\x00\x00\x00\x00\x00\n | u1 | s1
> As you can see, cqlsh can't display reversed type values properly ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira