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 <arodr...@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 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 <ty...@datastax.com>:
> > 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 <arodr...@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 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 <arodr...@gmail.com>
> >> >
> >> > 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 <tamil.3...@gmail.com>
> >> >
> >> >> 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 <http://datastax.com/>
