Thanks for the feedback... The Spring dependency is marked as optional<http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html>and will only be included as a dependency if you explicitly add it to your project. You only need to include it in your project if you want to use the Spring specific classes in the org.scale7.cassandra.pelops.spring package (seems a bit excessive to create a separate module for one class IMO)...
2011/1/23 Noble Paul നോബിള് नोब्ळ् <noble.p...@gmail.com> > I looked at pelops and found the API clean, but didn't like the spring > dependency. Hector API's could have been simpler but I plan to > abstract the most commonly used functionality in a simpler set of APIs > > On Thu, Jan 20, 2011 at 11:06 AM, Dan Washusen <d...@reactive.org> wrote: > > Pelops is pretty thin wrapper for the Thrift API. It's thinness has both > up > > and down sides; on the up side it's very easy to map functionality > mentioned > > on the Cassandra API wiki page to functionality provided by Pelops, it is > > also relatively simple to add features (thanks to Alois^^ for indexing > > support). The down side is you often have to deal with the Cassandra > Thrift > > classes like ColumnOrSuperColumn... > > On 20 January 2011 15:58, Dan Retzlaff <dretzl...@gmail.com> wrote: > >> > >> My team switched our production stack from Hector to Pelops a while > back, > >> based largely on this admittedly subjective "programmer experience" bit. > >> I've found Pelops' code and abstractions significantly easier to follow > and > >> integrate with, plus Pelops has had feature-parity with Hector for all > of > >> our use cases. It's quite possible that we just caught Hector during its > >> transition to what Nate calls "v2" but for our part, with no disrespect > to > >> the Hector community intended, we've been quite happy with the > transition. > >> Dan > >> On Wed, Jan 19, 2011 at 3:30 PM, Jonathan Shook <jsh...@gmail.com> > wrote: > >>> > >>> Perhaps. I use hector. I have an bit of rework to do moving from .6 to > >>> .7. This is something I wasn't anticipating in my earlier planning. > >>> Had Pelops been around when I started using Hector, I would have > >>> probably chosen it over Hector. The Pelops client seemed to be better > >>> conceived as far as programmer experience and simplicity went. Since > >>> then, Hector has had a "v2" upgrade to their API which breaks much of > >>> the things that you would have done in version .6 and before. > >>> Conceptually speaking, they appear more similar now than before the > >>> Hector changes. > >>> > >>> I'm dreading having to do a significant amount of work on my client > >>> interface because of the incompatible API changes.. but I will have to > >>> in order to get my client/server caught up to the currently supported > >>> branch. That is just part of the cost of doing business with Cassandra > >>> at the moment. Hopefully after "1.0" on the server and some of the > >>> clients, this type of thing will be more unusual. > >>> > >>> > >>> 2011/1/19 Noble Paul നോബിള് नोब्ळ् <noble.p...@gmail.com>: > >>> > Thanks everyone. I guess, I should go with hector > >>> > > >>> > On 18 Jan 2011 17:41, "Alois Bělaška" <alois.bela...@gmail.com> > wrote: > >>> >> Definitelly Pelops https://github.com/s7/scale7-pelops > >>> >> > >>> >> 2011/1/18 Noble Paul നോബിള് नोब्ळ् <noble.p...@gmail.com> > >>> >> > >>> >>> What is the most commonly used java client library? Which is the > the > >>> >>> most > >>> >>> mature/feature complete? > >>> >>> Noble > >>> >>> > >>> > > >> > > > > > > > > -- > ----------------------------------------------------- > Noble Paul | Systems Architect| AOL | http://aol.com >
