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.
: 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.
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
often (for example, if you are using WAN) better to try something else
first
: 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.
--
Sasha Dolgy
sasha.do
-40 concurrent clients.
I am kind of confused about which high level java client should I use ?
(Which one is the best/fastest for concurrent read operations)
Hector, Pelops, Astyanax, or something else ?
I browsed the mailing list, but I came across different types of arguments
which high level java client should I use ?
(Which one is the best/fastest for concurrent read operations)
Hector, Pelops, Astyanax, or something else ?
I browsed the mailing list, but I came across different types of arguments
and conclusions on behalf of various clients.
Thanks in advance,
James
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
