cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmet AKYOL (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-4362) cqlsh can't display reversed type values properly
Date Wed, 20 Jun 2012 18:14:42 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397709#comment-13397709
] 

Ahmet AKYOL edited comment on CASSANDRA-4362 at 6/20/12 6:13 PM:
-----------------------------------------------------------------

It's OK for me, not a big deal.  However, "clients shouldn't have to care about it" must mean
"cqlsh displays reversed type properly", right ?

What I mean is, yes reversed part is a server side optimization, but as clients, we don't
care unless we get the proper results  :) 
                
      was (Author: liqusha):
    It's OK for me, not a big deal.  However, "clients shouldn't have to care about it" must
mean "cqlsh displays reversed type properly", right :) 

What I mean is, yes reversed part is a server side optimization, but as clients, we don't
care unless we get the proper results...
                  
> 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
>            Priority: Minor
>              Labels: cqlsh
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message