Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1349598B5 for ; Fri, 11 May 2012 18:15:04 +0000 (UTC) Received: (qmail 39779 invoked by uid 500); 11 May 2012 18:15:01 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 39683 invoked by uid 500); 11 May 2012 18:15:01 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 39675 invoked by uid 99); 11 May 2012 18:15:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2012 18:15:01 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tyler@datastax.com designates 209.85.217.172 as permitted sender) Received: from [209.85.217.172] (HELO mail-lb0-f172.google.com) (209.85.217.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2012 18:14:56 +0000 Received: by lbbgo11 with SMTP id go11so2389665lbb.31 for ; Fri, 11 May 2012 11:14:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=CnalDmit9o/9vGFQ0Nb6hXTlG5ZTwekjzv35zBbQZ78=; b=FfuNxrDJmasPQsrVP2y6MxjZQ7o3chu7MpHN3b6AR9LGX6qumAJJF4ARScHFM6ZjLa qMp0L+xE4/E+jrdLbbPCcQdN7YoABPSyOPN2ZY7kH71gn6pHnXvUWJMpSvEuIe10PO7W lNPIh7AQdi3JhlQgmme3Q+4JvzT0/ZXpI95oKMue+OZMSPSI0kAOJFGoqEtE/Oea6sgK 9C52uzZ7H0CoH9BzpGUzHsz3gY69WmASpaLSaNr68RKmwBaCZs1jbjJDvY+DanLplzIA KU6exvcxoGoT326WBJlKFSjK3tSWOHt4b65Qsz3a/PHZYn/UsW4t0CnC1OnO0T0Y9XXb icag== MIME-Version: 1.0 Received: by 10.152.147.100 with SMTP id tj4mr9201159lab.39.1336760074526; Fri, 11 May 2012 11:14:34 -0700 (PDT) Received: by 10.112.27.137 with HTTP; Fri, 11 May 2012 11:14:34 -0700 (PDT) In-Reply-To: References: Date: Fri, 11 May 2012 13:14:34 -0500 Message-ID: Subject: Re: Thrift error occurred during processing of message From: Tyler Hobbs To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=e89a8f22bd89645f4e04bfc6b556 X-Gm-Message-State: ALoCoQk+Uhr8uUJ1oT0KnIP5HSt2HTpLfoluFuBBK5dMkqUlLSjDJziYGCLZ3ypU24r07+7YB44d X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f22bd89645f4e04bfc6b556 Content-Type: text/plain; charset=ISO-8859-1 If you're only fetching a single column and you know its name, use the second form. However, they should both technically work. I introduced it because PHP only has positional parameters and most of the parameters are optional, so having 6 or 10 parameters was annoying when you only needed to set the last one. On Fri, May 11, 2012 at 1:00 PM, Alain RODRIGUEZ wrote: > Thank you for the fast answer Tylor, I just discover the existence of > the "ColumnSlice" class. I was using phpcassa for a while and didn't > notice about this evolution. > > If I want to get just a column should I do : > > $slice = new ColumnSlice('name', 'name'); > $result = $cf->get($key, $slice); > > or > > $result = $cf->get($key, null, array('name')); > > Is there any difference on performance between this 2 solution ? Do > they both work ? > > Why introducing ColumnSlice ? > > Alain > > 2012/5/11 Tyler Hobbs : > > Can you paste a snippet of your code showing how you're creating the > > ColumnSlice and calling get()? > > > > > > On Fri, May 11, 2012 at 8:16 AM, Alain RODRIGUEZ > wrote: > >> > >> I got the error above in cassandra logs. > >> > >> In my web browser I have the following error : > >> > >> "500 | Internal Server Error | TApplicationException > >> > >> Required field 'reversed' was not found in serialized data! Struct: > >> SliceRange(start:80 01 00 01 00 00 00 0E 6D 75 6C 74 69 67 65 74 5F 73 > >> 6C 69 63 65 00 00 00 00 0F 00 01 0B 00 00 00 01 00 00 00 01 31 0C 00 > >> 02 0B 00 03 00 00 00 11 61 6C 67 6F 5F 70 72 6F 64 75 63 74 5F 76 69 > >> 65 77 00 0C 00 03 0C 00 02 0B 00 01 00 00 00 00, finish:80 01 00 01 00 > >> 00 00 0E 6D 75 6C 74 69 67 65 74 5F 73 6C 69 63 65 00 00 00 00 0F 00 > >> 01 0B 00 00 00 01 00 00 00 01 31 0C 00 02 0B 00 03 00 00 00 11 61 6C > >> 67 6F 5F 70 72 6F 64 75 63 74 5F 76 69 65 77 00 0C 00 03 0C 00 02 0B > >> 00 01 00 00 00 00 0B 00 02 00 00 00 00, reversed:false, count:100)" > >> > >> I think I forgot something that may have changed in the new phpcassa > >> release. I'm still looking for it but any Idea is welcome :) > >> > >> Alain > >> > >> 2012/5/11 Alain RODRIGUEZ > >> > > >> > Hi, I guess you finally solved this issue. I'm experimenting the same > >> > one when trying to upgrade to phpcass 1.0.a.1. > >> > > >> > Do you remember how you fixed it or what the problem was exactly ? > >> > > >> > Thanks, > >> > > >> > Alain > >> > > >> > 2011/12/19 Tamil selvan R.S > >> > > >> >> Hi, > >> >> We are using PHPCassa to connect to Cassandra 1.0.2. After we > >> >> installed the thrift extension we started noticing the following in > the > >> >> error logs. [We didn't notice this when we were running raw thrift > library > >> >> with out extension]. > >> >> > >> >> ERROR [pool-2-thread-5314] 2011-12-05 20:26:47,729 > >> >> CustomTThreadPoolServer.java (line 201) Thrift error occurred during > >> >> processing of message. > >> >> org.apache.thrift.protocol. > >> >> TProtocolException: Missing version in readMessageBegin, old client? > >> >> at > >> >> > org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:213) > >> >> at > >> >> > org.apache.cassandra.thrift.Cassandra$Processor.process(Cassandra.java:2877) > >> >> at > >> >> > org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:187) > >> >> at > >> >> > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > >> >> at > >> >> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > >> >> at java.lang.Thread.run(Thread.java:722) > >> >> > >> >> Is there any issue with the thrift protocol compatibilty? > >> >> > >> >> Regards, > >> >> Tamil > >> > > >> > > > > > > > > > > > -- > > Tyler Hobbs > > DataStax > > > -- Tyler Hobbs DataStax --e89a8f22bd89645f4e04bfc6b556 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If you're only fetching a single column and you know its name, use the = second form. However, they should both technically work.

I introduce= d it because PHP only has positional parameters and most of the parameters = are optional, so having 6 or 10 parameters was annoying when you only neede= d to set the last one.

On Fri, May 11, 2012 at 1:00 PM, Alain RODRI= GUEZ <arodrime@gmail.com> wrote:
Thank you for the fast answer Tylor, I just discover the existence of
the "ColumnSlice" class. I was using phpcassa for a while and did= n't
notice about this evolution.

If I want to get just a column should I do :

$slice =A0=3D new ColumnSlice('name', 'name');
$result =3D $cf->get($key, $slice);

or

$result =3D $cf->get($key, null, array('name'));

Is there any difference on performance between this 2 solution ? Do
they both work ?

Why introducing ColumnSlice ?

Alain

2012/5/11 Tyler Hobbs <tyler@datas= tax.com>:
> Can you paste a snippet of you= r code showing how you're creating the
> ColumnSlice and calling get()?
>
>
> On Fri, May 11, 2012 at 8:16 AM, Alain RODRIGUEZ <arodrime@gmail.com> wrote:
>>
>> I got the error above in cassandra logs.
>>
>> In my web browser I have the following error :
>>
>> "500 | Internal Server Error | TApplicationException
>>
>> Required field 'reversed' was not found in serialized data= ! Struct:
>> SliceRange(start:80 01 00 01 00 00 00 0E 6D 75 6C 74 69 67 65 74 5= F 73
>> 6C 69 63 65 00 00 00 00 0F 00 01 0B 00 00 00 01 00 00 00 01 31 0C = 00
>> 02 0B 00 03 00 00 00 11 61 6C 67 6F 5F 70 72 6F 64 75 63 74 5F 76 = 69
>> 65 77 00 0C 00 03 0C 00 02 0B 00 01 00 00 00 00, finish:80 01 00 0= 1 00
>> 00 00 0E 6D 75 6C 74 69 67 65 74 5F 73 6C 69 63 65 00 00 00 00 0F = 00
>> 01 0B 00 00 00 01 00 00 00 01 31 0C 00 02 0B 00 03 00 00 00 11 61 = 6C
>> 67 6F 5F 70 72 6F 64 75 63 74 5F 76 69 65 77 00 0C 00 03 0C 00 02 = 0B
>> 00 01 00 00 00 00 0B 00 02 00 00 00 00, reversed:false, count:100)= "
>>
>> I think I forgot something that may have changed in the new phpcas= sa
>> release. I'm still looking for it but any Idea is welcome :) >>
>> Alain
>>
>> 2012/5/11 Alain RODRIGUEZ <arodrime@gmail.com>
>> >
>> > Hi, I guess you finally solved this issue. I'm experiment= ing the same
>> > one when trying to upgrade to phpcass 1.0.a.1.
>> >
>> > Do you remember how you fixed it or what the problem was exac= tly ?
>> >
>> > Thanks,
>> >
>> > Alain
>> >
>> > 2011/12/19 Tamil selvan R.S <tamil.3758@gmail.com>
>> >
>> >> Hi,
>> >> =A0We are using PHPCassa to connect to Cassandra 1.0.2. A= fter we
>> >> installed the thrift extension we started noticing the fo= llowing in the
>> >> error logs. [We didn't notice this when we were runni= ng raw thrift library
>> >> with out extension].
>> >>
>> >> ERROR [pool-2-thread-5314] 2011-12-05 20:26:47,729
>> >> CustomTThreadPoolServer.java (line 201) Thrift error occu= rred during
>> >> processing of message.
>> >> org.apache.thrift.protocol.
>> >> TProtocolException: Missing version in readMessageBegin, = old client?
>> >> =A0=A0=A0 at
>> >> org.apache.thrift.protocol.TBinaryProtocol.readMessageBeg= in(TBinaryProtocol.java:213)
>> >> =A0=A0=A0 at
>> >> org.apache.cassandra.thrift.Cassandra$Processor.process(C= assandra.java:2877)
>> >> =A0=A0=A0 at
>> >> org.apache.cassandra.thrift.CustomTThreadPoolServer$Worke= rProcess.run(CustomTThreadPoolServer.java:187)
>> >> =A0=A0=A0 at
>> >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadP= oolExecutor.java:1110)
>> >> =A0=A0=A0 at
>> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(Thread= PoolExecutor.java:603)
>> >> =A0=A0=A0 at java.lang.Thread.run(Thread.java:722)
>> >>
>> >> Is there any issue with the thrift protocol compatibilty?=
>> >>
>> >> Regards,
>> >> Tamil
>> >
>> >
>
>
>
>
> --
> Tyler Hobbs
> DataStax
>



--
Tyler Hobbs
DataStax
<= br> --e89a8f22bd89645f4e04bfc6b556--