e right way to right that is to just say struct.name, struct.value, etc
>>> 2. why are you writing raw thrift instead of using Hector?
>>>
>>> On Fri, Jun 17, 2011 at 5:03 AM, Vivek Mishra
>>> wrote:
>>>>
>>>>
>>>>
>>
On Fri, Jun 17, 2011 at 5:03 AM, Vivek Mishra
>> wrote:
>>>
>>>
>>>
>>>
>>> From: Vivek Mishra
>>> Sent: Friday, June 17, 2011 3:25 PM
>>> To: user@cassandra.apache.org
>>> Subject: getFieldValue()
>>>
>&
A good example for what I understand in using Hector / pycassa / etc.
is, if you wanted to implement connection pooling, you would have to
craft your own solution, versus implementing the solution that is
tested and ready to go, provided by Hector. Thrift doesn't provide
native connection pooling
ead of using Hector?
>
> On Fri, Jun 17, 2011 at 5:03 AM, Vivek Mishra
> wrote:
>>
>>
>>
>>
>> From: Vivek Mishra
>> Sent: Friday, June 17, 2011 3:25 PM
>> To: user@cassandra.apache.org
>> Subject: getFieldValue()
>>
>>
>
@cassandra.apache.org
> Subject: getFieldValue()
>
>
>
> Hi,
>
> I was looking into getFieldValue method for SuperColumn and SlicePredicate
> apis.
>
>
>
> It looks to me slight confusing as underlying APIs are returning Object and
> developer can only be aware of ty
From: Vivek Mishra
Sent: Friday, June 17, 2011 3:25 PM
To: user@cassandra.apache.org
Subject: getFieldValue()
Hi,
I was looking into getFieldValue method for SuperColumn and SlicePredicate
apis.
It looks to me slight confusing as underlying APIs are returning Object and
developer can only