incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian O'Neill" <b...@alumni.brown.edu>
Subject TSocket read 0 bytes from cqlsh
Date Thu, 04 Oct 2012 19:04:07 GMT
This is probably already on your radar, but we could use a better
error message from cqlsh when the column key doesn't conform to the
expected schema...

I accidentally inserted data using Astyanax that didn't conform to the
schema.  After that, selects from that table via cqlsh return no
useful information.
(CLI shows the data just fine)


bone@boneill-macbook-wired:~/tools/cassandra-> bin/cassandra-cli
Connected to: "Test Cluster" on 127.0.0.1/9160
Welcome to Cassandra CLI version 1.1.5

Type 'help;' or '?' for help.
Type 'quit;' or 'exit;' to quit.

[default@unknown] use cirrus;
Authenticated to keyspace: cirrus
[default@cirrus] list data;
Using default limit of 100
Using default column limit of 100
-------------------
RowKey: PI7JC8
=> (column=*****, value=2014-07-31, timestamp=1349376866686000)
-------------------
RowKey: PI1234
=> (column=*****, value=Y, timestamp=1349372660453000)

2 Rows Returned.
Elapsed time: 212 msec(s).
[default@cirrus] quit;
bone@boneill-macbook-wired:~/tools/cassandra-> bin/cqlsh -3
Connected to Test Cluster at localhost:9160.
[cqlsh 2.2.0 | Cassandra 1.1.5 | CQL spec 3.0.0 | Thrift protocol 19.32.0]
Use HELP for help.
cqlsh> use cirrus;
cqlsh:cirrus> select * from data;
TSocket read 0 bytes
cqlsh:cirrus>

-- 
Brian ONeill
Lead Architect, Health Market Science (http://healthmarketscience.com)
mobile:215.588.6024
blog: http://brianoneill.blogspot.com/
twitter: @boneill42

Mime
View raw message