cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayadevan (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-5309) Issue in cassandra-cli and cqlsh
Date Mon, 04 Mar 2013 11:39:12 GMT
Jayadevan created CASSANDRA-5309:

             Summary: Issue in cassandra-cli and cqlsh
                 Key: CASSANDRA-5309
             Project: Cassandra
          Issue Type: Bug
          Components: Tools
    Affects Versions: 1.2.0
         Environment: Linus (CentOS), 64 bit.
            Reporter: Jayadevan
            Priority: Minor
             Fix For: 1.2.0

If I create a tabel using cqlsh, that table  does not show when I do a describe in cassandra-cli.
For example, I create a table in cqlsh.
cqlsh:system> CREATE KEYSPACE testkp WITH  replication =  {'class':'SimpleStrategy', 'replication_factor':2};

cqlsh:testkp> CREATE TABLE test (
          ...   k int PRIMARY KEY,
          ...   v1 int,
          ...   v2 int
          ... );

In cassandra-cli, I get this 

[default@testkp] show schema;
create keyspace testkp
  with placement_strategy = 'SimpleStrategy'
  and strategy_options = {replication_factor : 2}
  and durable_writes = true;

use testkp;

[default@testkp] describe;
Keyspace: testkp:
  Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
  Durable Writes: true
    Options: [replication_factor:2]
  Column Families:

No Column Family is show. But if I do 
[default@testkp] create column family test;
Cannot add already existing column family "test" to keyspace "testkp"
[default@testkp] list test;
Using default limit of 100
Using default column limit of 100
RowKey: 1
=> (column=, value=, timestamp=1362395851188000)
=> (column=v1, value=00000002, timestamp=1362395851188000)
=> (column=v2, value=00000003, timestamp=1362395851188000)

1 Row Returned.
Elapsed time: 105 msec(s).

So obviously the table/column family is there.

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:

View raw message