Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 337A211EEA for ; Mon, 2 Jun 2014 13:42:19 +0000 (UTC) Received: (qmail 34999 invoked by uid 500); 2 Jun 2014 13:42:17 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 34964 invoked by uid 500); 2 Jun 2014 13:42:17 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 34956 invoked by uid 99); 2 Jun 2014 13:42:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2014 13:42:17 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of woolfel@gmail.com designates 209.85.128.175 as permitted sender) Received: from [209.85.128.175] (HELO mail-ve0-f175.google.com) (209.85.128.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2014 13:42:14 +0000 Received: by mail-ve0-f175.google.com with SMTP id jw12so5134286veb.6 for ; Mon, 02 Jun 2014 06:41:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=CbZOslOsL/iy1ckClLBwTZdXaalKNawgpZPSFSDDbf0=; b=xppJCNJ54wApIB7RNULdQNfGkPbAvT1JiepyRh9c3oWV4g04mUq8BRsuNOwl53Txe/ RTpFCAf9/7jZdl0n7gFG4OocVE3nWaoXchIB1QSnImFypGr7Zji1qhLzLs3odUNOeuNt D4v/9JpQquG+iUindYXeipLAFQ7U7hYgp1x3Z8m9xsO1miOAc3cmunCvqK9K5hrsD8KB +r6y8MWaIQtHt4qi/Oe2TtMEJ34B7hSTTnSSOdwMQ/C52xFPNbMk+DAIwHj3VtlIyDk9 il7byPmf0HrbrF11NBV+ydxPjZp4IFmONwExvS3xzI/JJ7tzoYkXAKisg6ukGrdqJZdX pS/w== MIME-Version: 1.0 X-Received: by 10.220.44.141 with SMTP id a13mr308131vcf.71.1401716509949; Mon, 02 Jun 2014 06:41:49 -0700 (PDT) Received: by 10.221.17.198 with HTTP; Mon, 2 Jun 2014 06:41:49 -0700 (PDT) In-Reply-To: References: Date: Mon, 2 Jun 2014 09:41:49 -0400 Message-ID: Subject: Re: Nectar client - New Cassandra Client for .Net From: Peter Lin To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=047d7b343094a6c55c04fada8e53 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b343094a6c55c04fada8e53 Content-Type: text/plain; charset=UTF-8 I've studied DataStax .Net driver and it doesn't satisfy all of my needs. I wish it met 50% of my needs, but it doesn't. In theory, Nectar could use the DataStax .Net driver for native protocol, but I'd have to do a lot more work to make it fit with Hector's API. Some use cases can stick with CQL for 100%, but not the kinds of use cases I have. The modeler we built for Cassandra takes advantage of types, generics, Solr and tries to make it more friendly. We provide a JPA like interface for running queries and behind the scene the framework executes the queries against solr and cassandra. I know with DSE you can do a similar thing, but the developer has to build multiple queries themselves and tell cassandra to query solr. We take a model driven approach, so our schema modeler knows how to take advantage of the framework to run queries with "like" clauses. To the developer it's 1 query, not n queries. hopefully DataStax will accept my talk for september and we can show the stuff we built. On Mon, Jun 2, 2014 at 9:21 AM, Colin Clark wrote: > Peter, > > There's very little reason today to write your own Cassandra driver for > .net, java, or python. Those firms that do are now starting to wrap those > drivers with any specific functionality they might require, like Netflix, > for example. Have you looked at DataStax's .NET driver? > > -- > Colin > +1 320 221 9531 > > > > On Mon, Jun 2, 2014 at 7:38 AM, Peter Lin wrote: > >> >> thanks for the correction. Maybe it's just me, but I wish the >> implementation were also in apache's repo. It's not a big thing, but having >> multiple github forks to keep track of is a bit annoying. I'd rather spend >> time coding instead of screwing with git on windows. >> >> >> On Mon, Jun 2, 2014 at 8:29 AM, Benedict Elliott Smith < >> belliottsmith@datastax.com> wrote: >> >>> The native protocol specification has always been in the Apache >>> Cassandra repository. The implementations are not. >>> >>> >>> On 2 June 2014 13:25, Peter Lin wrote: >>> >>>> >>>> There's nothing preventing support for native protocol going forward. >>>> It was easier to go with thrift and I happen to like thirft. Native >>>> protocol is still relatively new, so I'm taking a wait and see approach.Is >>>> the native protocol specification and drivers still in DataStax's git? >>>> >>>> If it's going to be the "standard" protocol, then it really should be >>>> in apache's repo. That's my bias opinion. >>>> >>>> >>>> >>>> >>>> On Mon, Jun 2, 2014 at 8:16 AM, Colin Clark wrote: >>>> >>>>> Unless a cassandra driver is using the native protocol, it's going to >>>>> have a very short life going forward. >>>>> >>>>> -- >>>>> Colin >>>>> +1 320 221 9531 >>>>> >>>>> >>>>> >>>>> On Mon, Jun 2, 2014 at 7:10 AM, Peter Lin wrote: >>>>> >>>>>> >>>>>> it is using thrift. I've updated the project page to state that info. >>>>>> >>>>>> >>>>>> On Mon, Jun 2, 2014 at 8:08 AM, Colin Clark wrote: >>>>>> >>>>>>> Is your version of Hector using native protocol or thrift? >>>>>>> >>>>>>> -- >>>>>>> Colin >>>>>>> +1 320 221 9531 >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Mon, Jun 2, 2014 at 6:41 AM, Peter Lin wrote: >>>>>>> >>>>>>>> >>>>>>>> I'm happy to announce Concord has decided to open source our port >>>>>>>> of Hector to .Net. >>>>>>>> >>>>>>>> The project is hosted on google code >>>>>>>> https://code.google.com/p/nectar-client/ >>>>>>>> >>>>>>>> I'm still adding code documentation and wiki pages. It has been >>>>>>>> tested against 1.1.x, 2.0.x >>>>>>>> >>>>>>>> thanks >>>>>>>> >>>>>>>> peter >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > --047d7b343094a6c55c04fada8e53 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I've studied DataStax .Net dr= iver and it doesn't satisfy all of my needs. I wish it met 50% of my ne= eds, but it doesn't. In theory, Nectar could use the DataStax .Net driv= er for native protocol, but I'd have to do a lot more work to make it f= it with Hector's API. Some use cases can stick with CQL for 100%, but n= ot the kinds of use cases I have.

The modeler we built for Cassandra takes advantage of types, gene= rics, Solr and tries to make it more friendly. We provide a JPA like interf= ace for running queries and behind the scene the framework executes the que= ries against solr and cassandra. I know with DSE you can do a similar thing= , but the developer has to build multiple queries themselves and tell cassa= ndra to query solr. We take a model driven approach, so our schema modeler = knows how to take advantage of the framework to run queries with "like= " clauses. To the developer it's 1 query, not n queries.

hopefully DataStax will accept my talk for september and we can s= how the stuff we built.

=

On Mon, Jun 2, 2014 at 9:21 AM, Colin Cl= ark <colin@clark.ws> wrote:
Peter,

T= here's very little reason today to write your own Cassandra driver for = .net, java, or python. =C2=A0Those firms that do are now starting to wrap t= hose drivers with any specific functionality they might require, like Netfl= ix, for example. =C2=A0Have you looked at DataStax's .NET driver?



On Mon, Jun= 2, 2014 at 7:38 AM, Peter Lin <woolfel@gmail.com> wrote:

thanks for the correction. Maybe it's j= ust me, but I wish the implementation were also in apache's repo. It= 9;s not a big thing, but having multiple github forks to keep track of is a= bit annoying. I'd rather spend time coding instead of screwing with gi= t on windows.


On Mon,= Jun 2, 2014 at 8:29 AM, Benedict Elliott Smith <belliottsmith@da= tastax.com> wrote:
The native protocol specifi= cation has always been in the Apache Cassandra repository. The implementati= ons are not.


On = 2 June 2014 13:25, Peter Lin <woolfel@gmail.com> wrote:

There&#= 39;s nothing preventing support for native protocol going forward. It was e= asier to go with thrift and I happen to like thirft. Native protocol is sti= ll relatively new, so I'm taking a wait and see approach.Is the native = protocol specification and drivers still in DataStax's git?

If it's going to be the "standard" protocol, then i= t really should be in apache's repo. That's my bias opinion.



On Mon, Jun 2, 2014 at 8:16 AM, Colin Cl= ark <colin@clark.ws> wrote:
Unless a cassandra driver i= s using the native protocol, it's going to have a very short life going= forward.

On Mon, Jun 2, 2014 at 7= :10 AM, Peter Lin <woolfel@gmail.com> wrote:

it is using thrift. I've updated the pr= oject page to state that info.


=
On Mon, Jun 2, 2014 at 8:08 AM, Colin Clark <colin= @clark.ws> wrote:
Is your version of Hector u= sing native protocol or thrift?



On Mon, Jun 2, 2014 at 6:41 AM, Peter Li= n <woolfel@gmail.com> wrote:

I'm happy to announce Concord= has decided to open source our port of Hector to .Net.

The project = is hosted on google code https://code.google.com/p/nectar-client/

I'm still adding code documentation and wiki pages. It has be= en tested against 1.1.x, 2.0.x

thanks

peter








--047d7b343094a6c55c04fada8e53--