卡桑德拉净司机和CQL驱动程序(2012年8月)驱动程序、司机、卡桑德拉、CQL

由网友(泪是没有颜色的血)分享简介:问题已经被问过因此,关于这一点,但他们一岁多,所以我重新张贴。Questions have been asked on SO about this, but they are over a year old, so I'm re-posting.我不要求是最好的驱动程序,因为这是主观的。我在寻找有关稳定,符合最新的...

问题已经被问过因此,关于这一点,但他们一岁多,所以我重新张贴。

Questions have been asked on SO about this, but they are over a year old, so I'm re-posting.

我不要求是最好的驱动程序,因为这是主观的。我在寻找有关稳定,符合最新的卡桑德拉的功能,文档和易于使用的,和速度数据。

I'm not asking which is the "best" driver as that is subjective. I'm looking for data concerning stability, compliance to the latest Cassandra features, documentation and ease-of-use, and speed.

这似乎赫克托有(每Github上2年前)很少活动。所以这是卡桑德拉锐利,Fluentcassandra,Aquiles和Cassandraemo之间。

It seems Hector has little activity (2 years ago per Github). So it's between Cassandra-sharp, Fluentcassandra, Aquiles, and Cassandraemo.

我注意到一些做一些不提节俭API。什么是从.NET的角度来看的意义?

I noticed some do and some don't mention the Thrift API. What's the significance from a .Net perspective?

有一个定制列表的解决方案?

Is there a CQL solution?

推荐答案

FluentCassandra 有伟大的LINQ支持-to-CQL,它的类型系统是首屈一指的,而且目前正在推荐 DataStax 。它支持以下几种类型,并正确连接codeS它们使用Java的大端字节格式,使他们可以从其他库中读取。

FluentCassandra has great support for LINQ-to-CQL, it's type system is second to none, and it is currently being recommended by DataStax. It supports the following types, and properly encodes them using Java's big endian byte format so that they can be read from other libraries.

ASCII 布尔 字节 组合 计数器 日期 在小数 双击 动态合成 浮动 的Int32 在整数(其他明智称为大整数 - 任何超过64位) 词汇UUID 龙 时间UUID UTF8 UUID ASCII Boolean Bytes Composite Counter Date Decimal Double Dynamic Composite Float Int32 Integer (other wise known as Big Integer - anything beyond 64 bits) Lexical UUID Long Time UUID UTF8 UUID

大多数.NET库在那里只支持是在卡桑德拉初期发布的最初5。

Most of the .NET libraries out there only support the initial 5 that were released in the early days of Cassandra.

在我看来,我FluentCassandra的开发商,提用节俭是像提的是,.NET使用Win32 API的。我们围绕这些东西的库,因为作为发展他们臭的接口,并给最终用户,开发者,他们真的并不重要。

In my opinion, and I am the developer of FluentCassandra, mentioning the use of Thrift is like mentioning that .NET uses the Win32 API's. We have built libraries around these things, because as an interface for development they stink, and to the end-user-developer they really don't matter.

阅读全文

相关推荐

最新文章