after 1 year experience with Hector, i would recommend: stay away from
hector if possible.
I do not understand why everyone wants to force this issue on removing
thrift. If cql, cql sparse tables and the new transport are better people
will naturally begin to use them, but as it stands now I see the it
this way:
Thrift still has more clients for more languages, thrift has more higher
le
Hi,
I am working on a POC for cassandra 1.1.6 with hector 0.8.0-2.
It fails on a update with the following exception. Anyone has seen this error
before? Please could you help..
Hector throws an HectorException: Exception message : "All host pools marked
down. Retry burden pushed out to client.
I agree on 2.0.
For the thrift part, we've said clearly that we wouldn't remove it any time
soon so let's stick to that. Besides, I would agree it's too soon anyway.
What we can do however in the relatively short term on that front, is to
pull thrift in it's own jar (we've almost removed all inter
