I tried most of these solutions and find hector the best. Even when you have some problem you can always reach people who wrote hector in #cassandra in freenode. and the code is more mature as far as I concern. In cassandra client the most critical part would be connection pooling management (since all the clients do mostly the same operations through thrift, but connection pooling is what makes high level client roll). In that case I would vote for hector since I am using it in production for over a year now with no visible problem (1 reconnect issue fixed as soon as I discovered and send an email about it).
Documentation not bad, but the Java Docs are lacking a bit. That could easily be a Git fork / pull request by the user community.
The ORM support was a bit limited, but not urgent for usage in our case. I couldn't get some of the one-to-many associations to work easily, plus lack of describing what type of Cassandra model (super columns or column families for associated collections). Also a lack of Java examples (maybe there are some, please post if you find some).
Also, I tried using kundera with very little success. Not many examples to use or try, very little forum support. It appears to be maintained by one person, which makes it even hard to choose a tool like that. It appears based on the SVN activity it was migrating to using Hadoop instead or support for it as well.
I would propose also Astyanax, I'm working with it and I'm quite happy. Only the documentation is not really good.
Astyanax API
Astyanax implements a fluent API which guides the caller to narrow or customize the query via a set of well defined interfaces. We've also included some recipes that will be executed efficiently and as close to the low level RPC layer as possible. The client also makes heavy use of generics and overloading to almost eliminate the need to specify serializers. Some key features of the API include:
Key and column types are defined in a ColumnFamily class which eliminates the need to specify serializers.
Multiple column family key types in the same keyspace. Annotation based composite column names.
Automatic pagination.
Parallelized queries that are token aware.
Configurable consistency level per operation.
Configurable retry policy per operation.
Pin operations to specific node.
Async operations with a single timeout using Futures.
Simple annotation based object mapping.
Operation result returns host, latency, attempt count.
Tracer interfaces to log custom events for operation failure and success.
Optimized batch mutation.
Completely hide the clock for the caller, but provide hooks to customize it.
Simple CQL support.
RangeBuilders to simplify constructing simple as well as composite column ranges.
Composite builders to simplify creating composite column names.
Recipes Recipes for some common use cases:
CSV importer.
JSON exporter to convert any query result to JSON with a wide range of customizations.
I suggest you give Kundera-2.0.1 a try. It has gone a major change since its inception and I see a lot of new features getting added and bugs being fixed. Currently it supports JPA 1.0 and Cassandra 0.7.6 but they are planning to add support for Cassandra 0.8 and JPA 2.0 very soon. There is a pretty good example here: https://github.com/impetus-opensource/Kundera/wiki/Getting-Started-in-5-minutes
发布评论
评论（7）
我尝试了大部分解决方案，发现 hector 是最好的。即使您遇到一些问题，您也可以随时联系在 freenode 中的 #cassandra 中编写 hector 的人。而且就我而言，代码更加成熟。在 cassandra 客户端中，最关键的部分是连接池管理（因为所有客户端通过 thrift 执行大部分相同的操作，但连接池是使高级客户端滚动的原因）。在这种情况下，我会投票给赫克托，因为我在生产中使用它已经一年多了，没有任何明显的问题（当我发现并发送有关它的电子邮件后，就修复了 1 个重新连接问题）。
不过我仍在使用 cassandra 0.6。
I tried most of these solutions and find hector the best. Even when you have some problem you can always reach people who wrote hector in #cassandra in freenode. and the code is more mature as far as I concern. In cassandra client the most critical part would be connection pooling management (since all the clients do mostly the same operations through thrift, but connection pooling is what makes high level client roll). In that case I would vote for hector since I am using it in production for over a year now with no visible problem (1 reconnect issue fixed as soon as I discovered and send an email about it).
I am still using cassandra 0.6 though.
datanucleus 插件的作者 Todd Nine 现在正在 Hector 中致力于下一代 JPA 支持。
The author of the datanucleus plugin, Todd Nine, is working on the next-gen JPA support in Hector now.
Hector 客户端是我们选择的 API，因为它具有以下功能：
Hector 的缺点：
另外，我尝试使用昆德拉，但收效甚微。使用或尝试的例子不多，论坛支持也很少。它似乎是由一个人维护的，这使得选择这样的工具变得更加困难。它的出现是基于它正在迁移到的 SVN 活动，而是使用 Hadoop 或对其的支持。
The Hector client was the API that we choose because of the following things that it had:
Downside of Hector:
Also, I tried using kundera with very little success. Not many examples to use or try, very little forum support. It appears to be maintained by one person, which makes it even hard to choose a tool like that. It appears based on the SVN activity it was migrating to using Hadoop instead or support for it as well.
昆德拉2.0.4发布。
此版本中的主要变化：
Kundera 2.0.4 released.
Major Changes in this release:
我也建议使用 Astyanax，我正在使用它并且我很高兴。只是文档不太好。
http://techblog.netflix.com/2012/01/announcing-astyanax.html
I would propose also Astyanax, I'm working with it and I'm quite happy. Only the documentation is not really good.
http://techblog.netflix.com/2012/01/announcing-astyanax.html
我建议你尝试一下 Kundera-2.0.1。自推出以来，它发生了重大变化，我看到添加了许多新功能并修复了错误。目前它支持 JPA 1.0 和 Cassandra 0.7.6，但他们计划很快添加对 Cassandra 0.8 和 JPA 2.0 的支持。这里有一个很好的例子： https://github .com/impetus-opensource/Kundera/wiki/5 分钟入门
I suggest you give Kundera-2.0.1 a try. It has gone a major change since its inception and I see a lot of new features getting added and bugs being fixed. Currently it supports JPA 1.0 and Cassandra 0.7.6 but they are planning to add support for Cassandra 0.8 and JPA 2.0 very soon. There is a pretty good example here: https://github.com/impetus-opensource/Kundera/wiki/Getting-Started-in-5-minutes
您可以尝试 Achilles，这是我开发的一个新实体管理器，支持所有 CQL3 功能。
启动嵌入式 Cassandra 服务器进行测试的 JUnit 4 规则
还有更多...
有 2 种实现：Thrift 和 Thrift CQL
Thrift 版本在底层依赖于 Hector。
CQL 版本从 Datastax 中提取全新的 Java Driver Core 用于所有操作
快速参考此处
You can try Achilles, a new Entity Manager I've developed that supports all CQL3 features.
JUnit 4 Rule to start embedded Cassandra server for testing
And so more ...
There are 2 implementations: Thrift & CQL
The Thrift version relies on Hector under the hood.
The CQL version pulls the brand new Java Driver Core from Datastax for all operations
Quick reference here