Details
-
Bug
-
Status: Resolved
-
Low
-
Resolution: Fixed
-
64 Bit Ubuntu 11.04(full update), AMD64 + 8GB RAM + 500GB Hdd, Java 1.6.0_26, Cassandra 0.8.0 + 4GB heap, Cassandra CLI
-
Low
Description
I have a Column Family named 1105115.
I have inserted the CF with Hector, and it did not
throw any exception concerning the name of the
column.
If I am issuing the command
list 1105115;
I incur the following error:
[default@unknown] list 1105115;
Syntax error at position 5: mismatched input '1105115' expecting Identifier
I presume we are not to name CFs as integers?
Or is there something I am missing from
the bellow help content:
[default@unknown] help list;
list <cf>;
list <cf>[<startKey>:];
list <cf>[<startKey>:<endKey>];
list <cf>[<startKey>:<endKey>] limit <limit>;
List a range of rows, and all of their columns, in the specified column
family.
The order of rows returned is dependant on the Partitioner in use.
Required Parameters:
- cf: Name of the column family to list rows from.
Optional Parameters:
- endKey: Key to end the range at. The end key will be included
in the result. Defaults to an empty byte array.
- limit: Number of rows to return. Default is 100.
- startKey: Key start the range from. The start key will be
included in the result. Defaults to an empty byte array.
Examples:
list Standard1;
list Super1[j:];
list Standard1[j:k] limit 40;
================================================
Column Family Info:
ColumnFamily: 1105115
Key Validation Class: org.apache.cassandra.db.marshal.BytesType
Default column value validator: org.apache.cassandra.db.marshal.BytesType
Columns sorted by: org.apache.cassandra.db.marshal.AsciiType
Row cache size / save period in seconds: 0.0/0
Key cache size / save period in seconds: 200000.0/14400
Memtable thresholds: 0.5203125/111/1440 (millions of ops/MB/minutes)
GC grace seconds: 864000
Compaction min/max thresholds: 4/32
Read repair chance: 1.0
Replicate on write: true
Built indexes: []
Attachments
Attachments
Issue Links
- is related to
-
CASSANDRA-3054 CLI "drop index" doesn't handle numeric-only hex column identifiers properly
- Resolved