cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nate McCall <>
Subject Re: Cassandra Java Driver and DataStax
Date Sat, 04 Jun 2016 16:29:44 GMT
On Sat, Jun 4, 2016 at 10:05 AM, James Carman <>

> 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), current ASF committer (Usergrid) and active community
member since late 2009, my opinion is that this would be a step backwards.

Maintaining Hector independently allowed me the freedom to release major
features with technology that I wanted to use while maintaining backwards
compatibility without having to be bound to the project's release cycle and
process. (And to use a build system that didnt suck).

The initial concern of the use of the word "controls" is *super* not cool
and I hope that this is being fixed. That said, the reality, from my
(external to DataStax) perspective, is that this is not the case. I like
the current project separation the way it is and don't feel like there is
any attempt at "control" of the java driver's direction and development.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message