Re: Pelops - a new Java client library paradigm

On Mon, Jun 14, 2010 at 2:28 PM, Dominic Williams wrote: > Hi Todd, we're on 6 or 6.1 but I would hope it should work with 6.2 > We will also be moving to 6.2 very shortly because we need the column > timeout feature that a 6.2 patch has been submitted for (I haven't checked, > maybe that feature

Re: Pelops - a new Java client library paradigm

0. Have you built and/or >run Pelops against 0.6.2 or trunk? > > > > Todd > > > -- > > *From:* Dominic Williams [mailto:thedwilli...@googlemail.com] > *Sent:* Friday, June 11, 2010 6:42 AM > > *To:* user@cassandra.apache.o

RE: Pelops - a new Java client library paradigm

From: Dominic Williams [mailto:thedwilli...@googlemail.com] Sent: Friday, June 11, 2010 6:42 AM To: user@cassandra.apache.org Subject: Pelops - a new Java client library paradigm Pelops is a new high quality Java client library for Cassandra. It has a design that: * reveals

RE: Pelops - a new Java client library paradigm

assandra.apache.org<mailto:user@cassandra.apache.org> Subject: Re: Pelops - a new Java client library paradigm Hi good question. The scalability of Pelops is dependent on Cassandra, not the library itself. The library aims to provide an more effective access layer on top of the Thrift API.

Re: Pelops - a new Java client library paradigm

rashed node becomes available? > > > > Todd > > > -- > > *From:* Dominic Williams [mailto:thedwilli...@googlemail.com] > *Sent:* Friday, June 11, 2010 7:05 AM > *To:* user@cassandra.apache.org > *Subject:* Re: Pelops - a new Java client library parad

RE: Pelops - a new Java client library paradigm

s good for all. Thanks, Regards, Dop -Original Message- From: Torsten Curdt [mailto:tcu...@vafer.org] Sent: Monday, June 14, 2010 7:22 PM To: user@cassandra.apache.org Subject: Re: Pelops - a new Java client library paradigm Also think this looks really promising. The fact that there a

RE: Pelops - a new Java client library paradigm

y are used? Conversely, how will the pool be repopulated once the failed/crashed node becomes available? Todd From: Dominic Williams [mailto:thedwilli...@googlemail.com] Sent: Friday, June 11, 2010 7:05 AM To: user@cassandra.apache.org Subject: Re: Pelops - a new J

Re: Pelops - a new Java client library paradigm

That's the tradeoff we made to get basic functionality for a dozen or so languages for free; it's impossible to be idiomatic with Thrift. The glass-half-full view is, having lots of API wrappers shows that building on Thrift is far easier than throwing bytes around at the socket layer the way a tr

Re: Pelops - a new Java client library paradigm

Hi Riyad, No problem. Because it is a new library, I cannot provide a large list of production deployments. However, there are various reasons you should have confidence in the library:- 1/ Firstly the background of Pelops is that it is being used as the basis of a serious commercial project that

Re: Pelops - a new Java client library paradigm

Also think this looks really promising. The fact that there are so many API wrappers now (3?) doesn't reflect well on the native API though :) /me ducks and runs On Mon, Jun 14, 2010 at 11:55, Dominic Williams wrote: > Hi Ran, thanks for the compliment. It is true that we benefited enormously >

Re: Pelops - a new Java client library paradigm

Hi Ran, thanks for the compliment. It is true that we benefited enormously from batch mutate. Without that the Mutator/Selector paradigm would not have been possible in the same way. It will be interesting to see where Cassandra takes us next. Best, Dominic On 12 June 2010 20:05, Ran Tavory wrote

Re: Pelops - a new Java client library paradigm

Thanks for clarifying! On 13 June 2010 09:03, Miguel Verde wrote: > afaik, Cassandra does nothing to guarantee connection-level read your own > writes consistency beyond its usual consistency levels. See > https://issues.apache.org/jira/browse/CASSANDRA-876 and the earlier >

Re: Pelops - a new Java client library paradigm

afaik, Cassandra does nothing to guarantee connection-level read your own writes consistency beyond its usual consistency levels. See https://issues.apache.org/jira/browse/CASSANDRA-876 and the earlier http://issues.apache.org/jira/browse/CASSANDRA-132 On Jun 12, 2010, at 5:48 PM, Dan Washu

Re: Pelops - a new Java client library paradigm

Very nice! You mention that the connections are handled internally by Pelops, does that mean that potentially a different connection is used for each operation performed? I had assumed using the same connection for several operations with ConsistencyLevel.ONE would provide a basic level of atomic

Re: Pelops - a new Java client library paradigm

Nice going, Dominic, having a clear API for cassandra is a big step forward :) Interestingly, at hector we came up with similar approach, just didn't find the time for code that, as production systems keep me busy at nights as well... We started with the implementation of BatchMutation, but the res

Re: Pelops - a new Java client library paradigm

Dominic, I like the API; reads clearly and fairly intuitive. I think Ian was asking about what large-scale production deployments Pelops has been deployed in that you could speak to -- he's trying to get a confidence index and I am interested as well ;) Best, Riyad On Fri, Jun 11, 2010 at 7:04

Re: Pelops - a new Java client library paradigm

Hi good question. The scalability of Pelops is dependent on Cassandra, not the library itself. The library aims to provide an more effective access layer on top of the Thrift API. The library does perform connection pooling, and you can control the size of the pool and other parameters using a po

Re: Pelops - a new Java client library paradigm

Sounds nice. Can you say something about the scales at which you've used this library? Both write and read load? Size of clusters and size of data? Ian On Fri, Jun 11, 2010 at 9:41 AM, Dominic Williams < thedwilli...@googlemail.com> wrote: > Pelops is a new high quality Java client library fo

Pelops - a new Java client library paradigm

Pelops is a new high quality Java client library for Cassandra. It has a design that: * reveals the full power of Cassandra through an elegant "Mutator and Selector" paradigm * generates better, cleaner, less bug prone code * reduces the learning curve for new users * drives rapid application deve