Pelops is a very thin wrapper over the Thrift client so that could be a good
option.
You could also check out a fork by the VMWare/Spring guys which adds full async
support: https://github.com/andrewswan/scale7-pelops. I'm not sure on the
state of it, but it seems promising...
On Thursday
>> -----Original Message-
>>> From: Radim Kolar [mailto:h...@filez.com]
>>> Sent: Thursday, June 28, 2012 5:06 AM
>>> To: user@cassandra.apache.org
>>> Subject: Re: which high level Java client
>>>
>>> i do not have
m> wrote:
>
>> I use Pelops and have been very happy. In my opinion the interface is
>> cleaner than that with Hector. I personally do like the serializer
>> business.
>>
>> -Original Message-
>> From: Radim Kolar [mailto:h...@filez.com]
>> Sen
...@filez.com]
> Sent: Thursday, June 28, 2012 5:06 AM
> To: user@cassandra.apache.org
> Subject: Re: which high level Java client
>
> i do not have experience with other clients, only hector. But timeout
> management in hector is really broken. If you expect your nodes to timeout
: Re: which high level Java client
i do not have experience with other clients, only hector. But timeout
management in hector is really broken. If you expect your nodes to timeout
often (for example, if you are using WAN) better to try something else first.
i do not have experience with other clients, only hector. But timeout
management in hector is really broken. If you expect your nodes to
timeout often (for example, if you are using WAN) better to try
something else first.
Hello
We are using Hector and it perfectly matching to our case.
https://github.com/hector-client/hector
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/which-high-level-Java-client-tp7580842p7580844.html
Sent from the cassandra-u...@incubator.a
