incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Evans <eev...@rackspace.com>
Subject Re: problem with running simple example using cassandra-cli with 0.6.0-beta2
Date Thu, 11 Mar 2010 18:22:13 GMT
On Wed, 2010-03-10 at 18:09 -0500, Bill Au wrote:
> I am checking out 0.6.0-beta2 since I need the batch-mutate function.
> I am just trying to run the example is the cassandra-cli Wiki:
> 
> http://wiki.apache.org/cassandra/CassandraCli
> 
> Here is what I am getting:
> 
> cassandra> set Keyspace1.Standard1['jsmith']['first'] = 'John'
> Value inserted.
> cassandra> get Keyspace1.Standard1['jsmith']
> => (column=6669727374, value=John, timestamp=1268261785077)
> Returned 1 results.
> 
> The column name being returned by get (6669727374) does not match what
> is set (first).  This is true for all column names.
> 
> cassandra> set Keyspace1.Standard1['jsmith']['last'] = 'Smith'
> Value inserted.
> cassandra> set Keyspace1.Standard1['jsmith']['age'] = '42'
> Value inserted.
> cassandra> get Keyspace1.Standard1['jsmith']
> => (column=6c617374, value=Smith, timestamp=1268262480130)
> => (column=6669727374, value=John, timestamp=1268261785077)
> => (column=616765, value=42, timestamp=1268262484133)
> Returned 3 results.
> 
> Is this a problem in 0.6.0-beta2 or am I doing anything wrong?

No, you're not doing anything wrong. What you're seeing is the hex
representation of a BytesType, which is the comparator that Standard1 in
the example config uses. This is the same for 0.5.1 too.

If you haven't made any changes to the default config, try using
Standard2 as the column family and you'll see a human-readable column
name as expected (Standard2 uses a UTF8Type comparator).

The wiki page has sample output that is confusing, (it's probably
cut-and-paste from a time when Standard1 used an ASCII or UTF8
comparator), we should probably fix that.

-- 
Eric Evans
eevans@rackspace.com


Mime
View raw message