Thanks. With 0.6.0-beta2 using Standard2 does show a human-readable column.
However, the behavior is definitely different between 0.5.1 and
0.6.0-beta2. I am using the binary distribution of 0.5.1:
cassandra show version
0.5.1
cassandra set Keyspace1.Standard1['jsmith']['first'] = 'John'
Value
On Fri, 2010-03-12 at 11:21 -0500, Bill Au wrote:
Thanks. With 0.6.0-beta2 using Standard2 does show a human-readable
column.
However, the behavior is definitely different between 0.5.1 and
0.6.0-beta2. I am using the binary distribution of 0.5.1:
cassandra show version
0.5.1
Thanks for clearing this up for me.
Bill
On Fri, Mar 12, 2010 at 11:49 AM, Eric Evans eev...@rackspace.com wrote:
On Fri, 2010-03-12 at 11:21 -0500, Bill Au wrote:
Thanks. With 0.6.0-beta2 using Standard2 does show a human-readable
column.
However, the behavior is definitely different
Yes, I was expecting the column names to come back as strings like the way
it does with 0.5.1.
Bill
On Thu, Mar 11, 2010 at 12:03 AM, Jonathan Ellis jbel...@gmail.com wrote:
I think he means how the column names are rendered as bytes but the
values are strings.
On Wed, Mar 10, 2010 at 5:22
On Wed, Mar 10, 2010 at 5:09 PM, Bill Au bill.w...@gmail.com 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
I think he means how the column names are rendered as bytes but the
values are strings.
On Wed, Mar 10, 2010 at 5:22 PM, Brandon Williams dri...@gmail.com wrote:
On Wed, Mar 10, 2010 at 5:09 PM, Bill Au bill.w...@gmail.com wrote:
I am checking out 0.6.0-beta2 since I need the batch-mutate
