cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Mello (JIRA)" <>
Subject [jira] Created: (CASSANDRA-1005) cassandra-cli doesn't work with system allowed column family names
Date Mon, 19 Apr 2010 20:35:52 GMT
cassandra-cli doesn't work with system allowed column family names

                 Key: CASSANDRA-1005
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 0.5, 0.6
         Environment: Windows XP 32 bit
            Reporter: James Mello
             Fix For: 0.5, 0.6

Given the following definitions for columns:


<Keyspace Name="NGram">


<ColumnFamily CompareWith="UTF8Type" Name="1GramR"/>

<ColumnFamily CompareWith="UTF8Type" Name="1GramL"/>


The appropriate keyspaces are created an persisteted on startup. When executing a query or
a set operation in the cassandra-cli, you end up with the following error:


cassandra> get NGram.1GramR['hte']

line 1:10 extraneous input '1' expecting Identifier

No such column family: GramR


Following the syntax of the grammer we can see the following:

: K_SET columnFamilyExpr '=' value -> ^(NODE_THRIFT_SET columnFamilyExpr value)


: table DOT columnFamily '[' rowKey ']'
( '[' a+=columnOrSuperColumn ']'
('[' a+=columnOrSuperColumn ']')?
-> ^(NODE_COLUMN_ACCESS table columnFamily rowKey ($a+)?)

// syntactic Elements
: Letter ( Alnum | '_' )*

There is a mismatch on what is appropriate values for this in the system. So either the restriction
needs to be lifted in the cli, or the system must have a way of honoring the names.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message