From user-return-35729-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Sat Aug 3 15:19:05 2013 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 361A810CE7 for ; Sat, 3 Aug 2013 15:19:05 +0000 (UTC) Received: (qmail 78958 invoked by uid 500); 3 Aug 2013 15:19:01 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 78935 invoked by uid 500); 3 Aug 2013 15:19:00 -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 78922 invoked by uid 99); 3 Aug 2013 15:18:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Aug 2013 15:18:59 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kwright@nanigans.com designates 216.82.243.202 as permitted sender) Received: from [216.82.243.202] (HELO mail1.bemta8.messagelabs.com) (216.82.243.202) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Aug 2013 15:18:53 +0000 Received: from [216.82.242.99:13753] by server-10.bemta-8.messagelabs.com id 05/04-06587-54F1DF15; Sat, 03 Aug 2013 15:18:29 +0000 X-Env-Sender: kwright@nanigans.com X-Msg-Ref: server-9.tower-131.messagelabs.com!1375543108!19990885!1 X-Originating-IP: [216.166.12.99] X-StarScan-Received: X-StarScan-Version: 6.9.11; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11252 invoked from network); 3 Aug 2013 15:18:29 -0000 Received: from out001.collaborationhost.net (HELO out001.collaborationhost.net) (216.166.12.99) by server-9.tower-131.messagelabs.com with RC4-SHA encrypted SMTP; 3 Aug 2013 15:18:29 -0000 Received: from AUSP01VMBX28.collaborationhost.net ([192.168.20.73]) by AUSP01MHUB08.collaborationhost.net ([10.2.8.243]) with mapi; Sat, 3 Aug 2013 10:17:33 -0500 From: Keith Wright To: "user@cassandra.apache.org" , Tony Anecito Date: Sat, 3 Aug 2013 10:17:32 -0500 Subject: Re: Choosing Java Driver for using Cassandra with Java EE7 Thread-Topic: Choosing Java Driver for using Cassandra with Java EE7 Thread-Index: Ac6QVvT+HL+9o/uuR3WWbIXFLsKaZwABZ5ea Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_sewv4932j4xjclbhdud22r4i1375541386634emailandroidcom_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_sewv4932j4xjclbhdud22r4i1375541386634emailandroidcom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I definitely recommend the datastax driver so long as you plan on using cql= 3. Its binary protocol allows multiplexing, is vnode token aware, and does= not require serialize/deserialize to thrift. We used astyanax before and = it did work well and has support (aka recipes) for standard usage cases lik= e scans. Tony Anecito wrote: I use the DataStax driver anm happy with it so far. Also, think about if dr= iver is being worked on as Cassandra gets updated since CQL version always = getting improved so driver needs to improve wth it. So if driver developers= not work on it often then you should not use it. Also, I think DataStax dr= iver might have more users so DataStax get mre feedback for improvements an= d fixes. Just my 1 cent. -Tony From: Andrew Cobley To: "" Sent: Saturday, August 3, 2013 6:30 AM Subject: Re: Choosing Java Driver for using Cassandra with Java EE7 I've used most of the java drivers under Glashfish without a problem. IMHO= it's really down to the functionality you require in your application. Th= e Java Driver form datastax has the lowest learning curve for any java pro= grammer familiar with JDBC and I believe deals with pool management. Just my .2 cents worth Andy On 3 Aug 2013, at 08:28, Jan Algermissen > wrote: > Hi, > > I plan on using Cassandra in a Java EE7 (Glassfish) project and I wonder = which driver I should pick. > > Can anyone make a recommendation which of the available drivers fits best= into a Java EE environment? > > (I looking for avoiding thread pool management issues mostly. I am not so= interested in a JPA integration) > > Jan The University of Dundee is a registered Scottish Charity, No: SC015096 --_000_sewv4932j4xjclbhdud22r4i1375541386634emailandroidcom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I definitely recommend the datastax driver so long as you plan =
on using cql3.  Its binary protocol allows multiplexing, is vnode token awa=
re, and does not require serialize/deserialize to thrift.  We used astyanax=
 before and it did work well and has support (aka recipes) for standard usa=
ge cases like scans.=0A=
=0A=
Tony Anecito <adanecito@yahoo.com> wrote:=0A=
=0A=
I use the DataStax d= river anm happy with it so far. Also, think about if driver is being worked= on as Cassandra gets updated since CQL version always getting improved so = driver needs to improve wth it. So if driver developers not work on it often then you should not use it. Also, I= think DataStax driver might have more users so DataStax get mre feedback f= or improvements and fixes.
 
Just my 1 cent.
-Tony

From:<= /span> Andrew Cobley <a.e.cobley@dundee.ac.uk>
To: "<user@cassandr= a.apache.org>" <user@cassandra.apache.org>
Sent: Saturday, August 3, 2= 013 6:30 AM
Subject: Re: Choosing Java = Driver for using Cassandra with Java EE7

I've used most of the java drivers under Glashfish without a problem. = IMHO it's really down to the functionality you require in your application= .  The Java Driver form datastax has the lowest learning curve  f= or any java programmer familiar with JDBC and I believe deals with pool management.

Just my .2 cents worth

Andy


On 3 Aug 2013, at 08:28, Jan Algermissen <jan.algermiss= en@nordsc.com> wrote:

> Hi,
>
> I plan on using Cassandra in a Java EE7 (Glassfish) project and I wond= er which driver I should pick.
>
> Can anyone make a recommendation which of the available drivers fits b= est into a Java EE environment?
>
> (I looking for avoiding thread pool management issues mostly. I am not= so interested in a JPA integration)
>
> Jan


The University of Dundee is a registered Scottish Charity, No: SC015096



--_000_sewv4932j4xjclbhdud22r4i1375541386634emailandroidcom_--