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 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 inserted. > > cassandra> set Keyspace1.Standard1['jsmith']['last'] = 'Smith' > > Value inserted. > > cassandra> set Keyspace1.Standard1['jsmith']['age'] = '42' > > Value inserted. > > cassandra> get Keyspace1.Standard1['jsmith'] > > => (column=last, value=Smith, timestamp=1268408466548) > > => (column=first, value=John, timestamp=1268408464036) > > => (column=age, value=42, timestamp=1268408468895) > > Returned 3 results. > > > > With 0.5.1 using Standard1 does show a human-readable column as > > documented > > in the Wiki. > > Right you are, my mistake. This changed in > https://issues.apache.org/jira/browse/CASSANDRA-661 (which occurred > between 0.5 and 0.6). > > > Not sure which one is the correct behavior here. > > The current behavior is correct. I'll update the examples to avoid > future confusion. > > -- > Eric Evans > eev...@rackspace.com > >
