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 C9EB911E1F for ; Mon, 2 Jun 2014 13:22:00 +0000 (UTC) Received: (qmail 96168 invoked by uid 500); 2 Jun 2014 13:21:52 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 96128 invoked by uid 500); 2 Jun 2014 13:21:52 -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 96119 invoked by uid 99); 2 Jun 2014 13:21:52 -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:21:52 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.192.54] (HELO mail-qg0-f54.google.com) (209.85.192.54) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2014 13:21:48 +0000 Received: by mail-qg0-f54.google.com with SMTP id q108so10708341qgd.27 for ; Mon, 02 Jun 2014 06:21:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=DD4JU1L9AFM5NsO2ShNnhXrvDK4tAOCOxU3jOKsogQc=; b=QVa01OBR+u8YJIz/kJpKFuV4O3jyEQsas0SsBBU1xaVv93pqeM3kWbLioPBOKs7oCE JLIGNaTjCfQqIqlAI7RjSRmI8bU4k5y/XqGCNl+0fP3cdcpUiX6C+kM9ZJUFqNLQG9QI 2YKOgYKbHHj3TdxaYtZmEEvNeR0iPLCJUo5g0wo+yAH++w1rwMTh0gpRxy+n5meWp8Be e74B4DQMSn8LlOydMAFw+csUQhBYpS2xmVxW2VQ7YJ19RcxOb8Q8tWaU+100lhL9MfIv YoR598ptl5BNc3sgOPREZPMq4Dql3rXFwRI6Xv21W3YnM/MeYm0QSWGNq28hI/Rv69ib /j1w== X-Gm-Message-State: ALoCoQm6FFBTRdcG2g5+3f/WuyOS6Vj3wpdFOWh4/KiBUX8CAyLUQQ4yyM8+1z/T9G3Ux6tiGxRi MIME-Version: 1.0 X-Received: by 10.224.29.211 with SMTP id r19mr23202550qac.47.1401715284805; Mon, 02 Jun 2014 06:21:24 -0700 (PDT) Received: by 10.140.25.238 with HTTP; Mon, 2 Jun 2014 06:21:24 -0700 (PDT) In-Reply-To: References: Date: Mon, 2 Jun 2014 08:21:24 -0500 Message-ID: Subject: Re: Nectar client - New Cassandra Client for .Net From: Colin Clark To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=047d7bdc85c6a0ba7104fada457f X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdc85c6a0ba7104fada457f Content-Type: text/plain; charset=UTF-8 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 >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> > --047d7bdc85c6a0ba7104fada457f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Peter,

There's very little reason t= oday to write your own Cassandra driver for .net, java, or python. =C2=A0Th= ose firms that do are now starting to wrap those drivers with any specific = functionality they might require, like Netflix, for example. =C2=A0Have you= looked at DataStax's .NET driver?

--
Colin
+1 320 221 9531



On Mon, Jun 2, 2014 at 7:38 AM, Peter Li= n <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







--047d7bdc85c6a0ba7104fada457f--