Crash in Cassandra-CLI

(5 posts) (2 voices)

• Started 8 months ago by vs
• Latest reply from vs
• This topic is not resolved

Tags:

No tags yet.

1. 

   vs
   Member

   Hi,

   I created a table in CQLsh -3.0 and inserted values into it.

   create table users (
   Id uuid PRIMARY KEY,
   Name varchar,
   Age int
   );

   insert into users(Id, Name, Age) values ('001', 'XYZ', '30');
   :
   :

   cqlsh:usertable> select * from users;
   id | age | name
   --------------------------------------+-----+--------
   1381b530-1dd2-11b2-0000-242d50cf1ffd | 30 | XYZ
   13816710-1dd2-11b2-0000-242d50cf1ffd | 28 | ABC
   13818e20-1dd2-11b2-0000-242d50cf1ffd | 30 | PQR

   However, when I attempt to insert new rows into this table from Cassandra-CLI interface, it crashes:

   [default@unknown] use usertable;
   Authenticated to keyspace: usertable
   [default@usertable]
   [default@usertable] set users['005']['name'] = 'MNO';
   log4j:WARN No appenders could be found for logger (org.apache.cassandra.config.DatabaseDescriptor).
   log4j:WARN Please initialize the log4j system properly.
   log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
   Cannot locate cassandra.yaml
   Fatal configuration error; unable to start server. See log for stacktrace.

   C:\Development\apache-cassandra-1.1.3\bin>

   Has anyone else observed a similar behavior.? Is there some incompatibility between CQLsh 3.0 and Cassandra-CLI?

   Thanks,
   VS

   Posted 8 months ago #
2. 

   xedin
   Member

   Hi, there is incompatibility between CQL3 and Thrift (which CLI uses) because CQL3 defined ColumnFamilies don't share some of the information to Thrift interface (e.g. component_index field of column which is essential for building a correct column name). But your exception is different - can you try running cassandra-cli from the cassandra root dir like ./bin/cassandra-cli ?

   Posted 8 months ago #
3. 

   vs
   Member

   I observe a similar behavior with CQLsh spec 2.0 as well which is a bit strange.

   A get query in Cassandra-CLI works fine after adding the index on column 'age' from CQLsh:
   [default@usertable] get users where age=30;

   Somehow, the combined use of CQLsh and CLI doesn't seem to be getting along fine.
   Just curious to know if someone else has tried this and observed a similar behavior.

   I tried running Cassandra-CLI from root directory, still the same!

   Thanks,
   VS

   Posted 8 months ago #
4. 

   xedin
   Member

   That's weird, where do you keep your cassandra.yaml config? Could be a packaging issue...

   Posted 8 months ago #
5. 

   vs
   Member

   C:\Development\apache-cassandra-1.1.3\bin -- The bin directory

   Cassandra.yaml in
   C:\Development\apache-cassandra-1.1.3\conf

   Posted 8 months ago #

RSS feed for this topic