Re: Cassandra Java Driver and DataStax

What a fun topic. I re-joined the list just for this. As I understand, it the nature of the Apache Software Licence any corporate entity is allows to produce open and closed source software based on Apache Cassandra, however the Cassandra name is a trademark of the ASF foundation. As I under it,

Re: Cassandra Java Driver and DataStax

On Sat, Jun 4, 2016 at 2:38 PM, Jonathan Ellis wrote: > FWIW, in very very ancient history we actually had the drivers in tree. It > sucked, because the people who wanted to contribute to the drivers were for > the most part not Committers, and the committers for the most part

Re: Cassandra Java Driver and DataStax

Hi Chris, On a similar note to what Andres mentioned, me and couple of other people have recently contributed index implementation (SASI), which significantly extends indexing capabilities of Apache Cassandra, and might be one of the biggest changes to the database in years. I'm a member

Re: Cassandra Java Driver and DataStax

> On Jun 5, 2016, at 4:33 PM, Mattmann, Chris A (3980) > wrote: > > Thanks for the info Jonathan. I think have assessed based on > the replies thus far, my studying of the archives and > commit and project history the following situation. > > Unfortunately it

Re: Cassandra Java Driver and DataStax

On Sun, Jun 5, 2016 at 3:20 PM, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: > #1 - a driver is needed to use Apache Cassandra right? As in, you > wouldn’t expect users of Apache Cassandra to get the database core > from the ASF, and then use it without a driver (from

Re: Cassandra Java Driver and DataStax

> A key portion of your software’s stack, a client driver to use it, exists outside of Apache in separate communities. This is an inherent risk to the project. That's not at all obvious to me. The driver you're concerned about is not under ASF, but it is Apache licensed, if DataStax took it in a

Re: Cassandra Java Driver and DataStax

The Apache Cassandra project has always left development of its drivers up to the community. The DataStax Java Driver is not part of the Apache Cassandra project, it is an open source project created by DataStax. You can find a large list of drivers for Cassandra here:

Re: Cassandra Java Driver and DataStax

I am a non-datastax-employee committer, and the large percentage of my commits are not reviewed by datastax exmployees. I see problems or areas of improvement in the code base, and directly commit them. No questions asked, no oversight, no direction at all from datastax or their employees. I

Re: Cassandra Java Driver and DataStax

Thanks for the info Jonathan. I think have assessed based on the replies thus far, my studying of the archives and commit and project history the following situation. Unfortunately it seems like there is a bit of control going on I’m going to call a spade a spade here. A key portion of your

Re: Cassandra Java Driver and DataStax

On Sun, Jun 5, 2016 at 8:32 AM, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: > 1. Is Apache Cassandra useful *without* a driver? That is, can > you use the database without a driver to connect to it or in the > real world would your users all have to download at least one >

Re: Cassandra Java Driver and DataStax

Hi Jake, Thanks for the email. So back to my 2 questions - and in particular #1 - a driver is needed to use Apache Cassandra right? As in, you wouldn’t expect users of Apache Cassandra to get the database core from the ASF, and then use it without a driver (from somewhere else?) Cheers, Chris

Re: Cassandra Java Driver and DataStax

Hi All, Thanks for the replies so far. A few last questions: 1. Is Apache Cassandra useful *without* a driver? That is, can you use the database without a driver to connect to it or in the real world would your users all have to download at least one driver in order to use the DB? 2. To confirm

Re: Cassandra Java Driver and DataStax

He already showed himself a good man by apologizing. Please, no more mudslinging. We're on the same team here. On Jun 4, 2016 2:22 PM, "Michael Kjellman" wrote: > No need to argue your point to me anymore. I've already tuned you out. > > These are good people who I

Re: Cassandra Java Driver and DataStax

No need to argue your point to me anymore. I've already tuned you out. These are good people who I consider my friends and insulting people just shows your arguments really have no merit. Good luck with your new driver contribution! I look forward to reviewing the code. Sent from my iPhone

Re: Cassandra Java Driver and DataStax

First off, full disclosure: contributor, committer, PMC member, and finally, Datastax employee, in about that order chronologically. All of the drivers, as far as I know, are Apache licensed, just as is Cassandra itself. There is no 'control', there is only momentum, since anyone can fork the

Re: Cassandra Java Driver and DataStax

The java-driver is fully Apache licensed. In the implausible scenario something like that happens, we can always simply fork it and start maintaining it ourselves. As long as java-driver community are good community citizens - as they are, and have been since day one - we are happy to have

Re: Cassandra Java Driver and DataStax

On Sat, Jun 4, 2016 at 12:07 PM, James Carman wrote: > > On Sat, Jun 4, 2016 at 1:05 PM Nate McCall wrote: > > > Whereas the health of my company and title rely heavily on a thriving open > > source community, yet Aleksey and I are in

Re: Cassandra Java Driver and DataStax

I apologized else-thread about that one. It was a low blow. Anyway, to answer your question. The Cassandra community wins! How do we know if they won't make you pay for the driver in the future (after all your code is written against it)? It has happened before. Also, the rest of the

Re: Cassandra Java Driver and DataStax

On Sat, Jun 4, 2016 at 1:05 PM Nate McCall wrote: > Whereas the health of my company and title rely heavily on a thriving open > source community, yet Aleksey and I are in agreement. Let's keep it up at > the level of the project and technical merits, please. > > Okay,

Re: Cassandra Java Driver and DataStax

An eloquent and powerful response, but please, reply to my points instead of resorting to ad hominem arguments. In practical terms, who would benefit from such a merge, and who is suffering from the current state of affairs? --  AY On 4 June 2016 at 18:03:05, James Carman

Re: Cassandra Java Driver and DataStax

Whereas the health of my company and title rely heavily on a thriving open source community, yet Aleksey and I are in agreement. Let's keep it up at the level of the project and technical merits, please. On Sat, Jun 4, 2016 at 12:02 PM, James Carman wrote: > "Sr.

Re: Cassandra Java Driver and DataStax

On Sat, Jun 4, 2016 at 1:02 PM Nate McCall wrote: > For me, most of the complexity would have been dealing with the governing > body :) > > Seriously though, being independant allowed me to experiment with things > like going directly to the internal Storage API from the

Re: Cassandra Java Driver and DataStax

"Sr. Software Engineer at DataStax", imagine that. On Sat, Jun 4, 2016 at 1:01 PM Aleksey Yeschenko wrote: > As a member of that governing body (Cassandra PMC), I would much prefer > not to deal with the drivers as well. > > And I’m just as certain that java-driver - and

Re: Cassandra Java Driver and DataStax

For me, most of the complexity would have been dealing with the governing body :) Seriously though, being independant allowed me to experiment with things like going directly to the internal Storage API from the client which would have definitely been -1'ed by some committers (rightly so as it

Re: Cassandra Java Driver and DataStax

As a member of that governing body (Cassandra PMC), I would much prefer not to deal with the drivers as well. And I’m just as certain that java-driver - and other driver communities - would much rather prefer to keep their process and organisation instead of being forced to conform to ours.

Re: Cassandra Java Driver and DataStax

How does it add more complexity by having one governing body (the PMC)? What I am suggesting is that the driver project be somewhat of a subproject or a "module". It can still have its own life cycle, just like it does now. On Sat, Jun 4, 2016 at 12:44 PM Nate McCall

Re: Cassandra Java Driver and DataStax

It doesnt. But then we add complexity in communicating and managing versions, releases, etc. to the project. Again, from my experience with hector, I just didnt want the hassle of owning that within the project confines. On Sat, Jun 4, 2016 at 11:30 AM, James Carman

Re: Cassandra Java Driver and DataStax

Who said the driver has to be released with the database? On Sat, Jun 4, 2016 at 12:29 PM Nate McCall wrote: > On Sat, Jun 4, 2016 at 10:05 AM, James Carman > wrote: > > > So why not just donate the Java driver and keep that in house?

Re: Cassandra Java Driver and DataStax

On Sat, Jun 4, 2016 at 10:05 AM, James Carman wrote: > So why not just donate the Java driver and keep that in house? Cassandra is > a Java project. Makes sense to me. > > I won't deny there is an argument to be made here, but as a former client maintainer (Hector),

Re: Cassandra Java Driver and DataStax

So why not just donate the Java driver and keep that in house? Cassandra is a Java project. Makes sense to me. On Sat, Jun 4, 2016 at 10:58 AM Jonathan Ellis wrote: > On Sat, Jun 4, 2016 at 8:59 AM, Chris Mattmann > wrote: > > > Thanks Jonathan. I’m

Re: Cassandra Java Driver and DataStax

On Sat, Jun 4, 2016 at 8:59 AM, Chris Mattmann wrote: > Thanks Jonathan. I’m starting to get a clearer idea of what’s > going on here. Do you think it was a walled garden in terms of > making reviews for incoming driver patches when you did have > them in the tree? Not

Re: Cassandra Java Driver and DataStax

Thanks Jonathan. I’m starting to get a clearer idea of what’s going on here. Do you think it was a walled garden in terms of making reviews for incoming driver patches when you did have them in the tree? What you are talking about in the first paragraph is precisely the reason that your community

Re: Cassandra Java Driver and DataStax

FWIW, in very very ancient history we actually had the drivers in tree. It sucked, because the people who wanted to contribute to the drivers were for the most part not Committers, and the committers for the most part weren't interested in reviewing drivers patches, and you have different,

Re: Cassandra Java Driver and DataStax

Thanks Jason for the information - I’m going to continue researching and hope more people will chime in that are on the PMC. Thank you. Cheers, Chris ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data

Re: Cassandra Java Driver and DataStax

This is the way our community has operated for at least the 6ish years I have been involved with it. The Apache project develops the database, others in the community develop drivers. It's the way we have always worked, I'm sorry if you don't like that. DataStax has released their driver

Re: Cassandra Java Driver and DataStax

As an Apache guy, one to another, seriously, how would you respond to that? > On Jun 3, 2016, at 9:33 PM, Jason Brown wrote: > > The client-server protocol is well defined in the Cassandra repo, so any one > may implement a client library for any language. However,

Re: Cassandra Java Driver and DataStax

The client-server protocol is well defined in the Cassandra repo, so any one may implement a client library for any language. However, it is a far from trivial task, so not many folks build their own. Thus, already-built drivers tend to become the de facto standard, but we (the Apache Cassandra

Re: Cassandra Java Driver and DataStax

You can find a very small list containing Hector and the DataStax driver. Hector was made obsolete by quite a few architecture changes (That I don’t disagree with) Claiming you have a large list of drivers is just dishonest. > On Jun 3, 2016, at 9:16 PM, J. D. Jordan

Re: Cassandra Java Driver and DataStax

> On Jun 3, 2016, at 9:14 PM, Jeff Jirsa wrote: > > > https://github.com/hector-client/hector So - that isn’t doing CQL, Right? > > https://github.com/Netflix/astyanax Upgrading to CQL? > > http://doanduyhai.github.io/Achilles/ > Which driver do you use? >

Re: Cassandra Java Driver and DataStax

The Apache Cassandra project has always left development of its drivers up to the community. The DataStax Java Driver is not part of the Apache Cassandra project, it is an open source project created by DataStax. You can find a large list of drivers for Cassandra here:

Re: Cassandra Java Driver and DataStax

https://github.com/hector-client/hector https://github.com/Netflix/astyanax http://doanduyhai.github.io/Achilles/ https://github.com/noorq/casser https://github.com/impetus-opensource/Kundera https://github.com/deanhiller/playorm - Jeff ( Not affiliated with datastax ) On 6/3/16,

Re: Cassandra Java Driver and DataStax

Fame and fortune awaits me? What does that mean? > On Jun 3, 2016, at 9:10 PM, Dave Brosius wrote: > > Here are just some of the drivers. > > https://wiki.apache.org/cassandra/ClientOptions > > There's tons more for the older thrift interface > >

Re: Cassandra Java Driver and DataStax

Here are just some of the drivers. https://wiki.apache.org/cassandra/ClientOptions There's tons more for the older thrift interface https://wiki.apache.org/cassandra/ClientOptionsThrift Being as the new interface is, well, newer, there are less options. If you'd like to write your own and

Re: Cassandra Java Driver and DataStax

How many Java drivers could you point out? Doesn’t it strike you slightly off that you’d not have a driver for a DB in the same project you found the DB? > On Jun 3, 2016, at 8:51 PM, Dave Brosius wrote: > > There are many drivers for cassandra, supplied by various

Re: Cassandra Java Driver and DataStax

There are many drivers for cassandra, supplied by various individuals and groups, one of those drivers was started by people at datastax which is available as an opensource project. The open source project is not open to any random person on the internet to commit to (just like any open

Cassandra Java Driver and DataStax

Hi All, I’m investigating something a few ASF members contacted me about and pointed out, so I’m hoping you can help guide me here as a community. I have heard that a company, DataStax, whose marketing material mentions it as the only Cassandra vendor, “controls” the Java Driver for Apache