cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Rogers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5628) cqlsh "copy to" fails when there are more than 21 columns
Date Mon, 10 Jun 2013 11:24:20 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ian Rogers updated CASSANDRA-5628:
----------------------------------

    Summary: cqlsh "copy to" fails when there are more than 21 columns  (was: cqlsh "copy
to" fails when there are more than 22 columns)
    
> cqlsh "copy to" fails when there are more than 21 columns
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-5628
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5628
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.12
>         Environment: ubuntu 13.04
> $ uname -a
> Linux ian 3.8.0-23-generic #34-Ubuntu SMP Wed May 29 20:22:58 UTC 2013 x86_64 x86_64
x86_64 GNU/Linux
> $ cqlsh --version
> cqlsh 2.2.0
> $ nodetool -h localhost version
> ReleaseVersion: 1.1.12
>            Reporter: Ian Rogers
>
> See the cqlsh script below. If you comment out the "c1" line then the "copy to" command
exports 0 rows even though the "select *" works fine!
> USE test_keyspace;
> DROP TABLE foo;
> CREATE TABLE foo (
> id varchar PRIMARY KEY,
> a0 varchar,
> a1 varchar,
> a2 varchar,
> a3 varchar,
> a4 varchar,
> a5 varchar,
> a6 varchar,
> a7 varchar,
> a8 varchar,
> a9 varchar,
> b0 varchar,
> b1 varchar,
> b2 varchar,
> b3 varchar,
> b4 varchar,
> b5 varchar,
> b6 varchar,
> b7 varchar,
> b8 varchar,
> b9 varchar,
> c0 varchar,
> -- c1 varchar, -- uncomment this line and the "copy" will fail even though the "select"
works fine!
> );
> insert into foo (id, a1) values ('foo', 'grum');
> select * from foo;
> copy foo to '/tmp/foo.csv';

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

Mime
View raw message