Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 30200 invoked from network); 12 Mar 2010 16:22:30 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 Mar 2010 16:22:30 -0000 Received: (qmail 89490 invoked by uid 500); 12 Mar 2010 16:21:53 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 89461 invoked by uid 500); 12 Mar 2010 16:21:52 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 89453 invoked by uid 99); 12 Mar 2010 16:21:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Mar 2010 16:21:52 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bill.w.au@gmail.com designates 209.85.221.177 as permitted sender) Received: from [209.85.221.177] (HELO mail-qy0-f177.google.com) (209.85.221.177) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Mar 2010 16:21:51 +0000 Received: by qyk7 with SMTP id 7so1363286qyk.21 for ; Fri, 12 Mar 2010 08:21:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=sTfU0N4HKTowWxNHAn/M2ZScJ4M4tQ6V78kAfRnjNMA=; b=d2xWxef6HrqrjUYkl+36yPoKvj32HtcUQGaSQG286TOBxBChmBg5eqdtYrQ1u3SSYO R3Pr7PKjq3RtUx7azAccT5LA/56DMvQeQzY2QzeA57TXLCbgEytKWEX1gPz2fnUrZk55 tV/irP/Iwc7qv/r6jl0rD7IWgILcX4FEWsAGs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=dH9nH0T/HNuhLHabL+/0oUz4VPOSPoOqQHpAFxLRIeFPAI86+9/SBYDyxhoGQmNu40 i7RiDo7YWhaomRaLPVGL0JdE4eWhf+0IpRMZIcmVLMTqmAeDAJrCc6yU51Esexo+cSpq Vr3pTmw204jT3bnJ/5ZjBfSgWDGlGPz064Nq0= MIME-Version: 1.0 Received: by 10.220.80.78 with SMTP id s14mr1268246vck.146.1268410889719; Fri, 12 Mar 2010 08:21:29 -0800 (PST) In-Reply-To: <1268331733.2220.25.camel@erebus.lan> References: <3b5f72031003101509m689281e2scae46f524675be65@mail.gmail.com> <1268331733.2220.25.camel@erebus.lan> Date: Fri, 12 Mar 2010 11:21:29 -0500 Message-ID: <3b5f72031003120821m4c897a81u4dd3ed1fcc5f723e@mail.gmail.com> Subject: Re: problem with running simple example using cassandra-cli with 0.6.0-beta2 From: Bill Au To: cassandra-user@incubator.apache.org Content-Type: multipart/alternative; boundary=0016364ec92c82d21804819cece1 --0016364ec92c82d21804819cece1 Content-Type: text/plain; charset=ISO-8859-1 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. Not sure which one is the correct behavior here. Bill On Thu, Mar 11, 2010 at 1:22 PM, Eric Evans wrote: > 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 > > --0016364ec92c82d21804819cece1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks.=A0 With 0.6.0-beta2 using Standard2 does show a human-readable colu= mn.

However, the behavior is definitely different between 0.5.1 and = 0.6.0-beta2.=A0 I am using the binary distribution of 0.5.1:

cassand= ra> show version=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
0.5.1
cassandra> set Keyspace1.Standard1['jsmith']['first= '] =3D 'John'
Value inserted.
cassandra> set Keyspace1= .Standard1['jsmith']['last'] =3D 'Smith'
Value i= nserted.
cassandra> set Keyspace1.Standard1['jsmith']['age'] =3D = '42'=A0=A0=A0
Value inserted.
cassandra> get Keyspace1.St= andard1['jsmith']=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0
=3D> (column=3Dlast, value=3DSmith, timestamp=3D1268408466548) =3D> (column=3Dfirst, value=3DJohn, timestamp=3D1268408464036)
=3D>= ; (column=3Dage, value=3D42, timestamp=3D1268408468895)
Returned 3 resul= ts.

With 0.5.1 using Standard1 does show a human-readable column as = documented in the Wiki.

Not sure which one is the correct behavior here.

Bill

On Thu, Mar 11, 2010 at 1:22 PM, Eric Evans <eevans@rackspace.com= > wrote:
<= div class=3D"h5">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.<= br> > 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'= ;] =3D 'John'
> Value inserted.
> cassandra> get Keyspace1.Standard1['jsmith']
> =3D> (column=3D6669727374, value=3DJohn, timestamp=3D1268261785077)=
> Returned 1 results.
>
> The column name being returned by get (6669727374) does not match what=
> is set (first). =A0This is true for all column names.
>
> cassandra> set Keyspace1.Standard1['jsmith']['last'= ] =3D 'Smith'
> Value inserted.
> cassandra> set Keyspace1.Standard1['jsmith']['age']= =3D '42'
> Value inserted.
> cassandra> get Keyspace1.Standard1['jsmith']
> =3D> (column=3D6c617374, value=3DSmith, timestamp=3D1268262480130)<= br> > =3D> (column=3D6669727374, value=3DJohn, timestamp=3D1268261785077)=
> =3D> (column=3D616765, value=3D42, timestamp=3D1268262484133)
> 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


--0016364ec92c82d21804819cece1--