cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Telford <>
Subject Re: Proposal: Moving CQL drivers
Date Fri, 09 Sep 2011 14:32:06 GMT
It may be prudent to have someone to accept responsibility for each of the
official drivers in Extras. This way we could have a single ticket (perhaps
with sub-tickets for each driver) to ensure drivers are brought up to date
for each release.

This would be less about polluting the C* JIRA with implementation details
for each driver, more of a place for driver maintainers to report-in that a
driver is compatible with an impending release.

This would also make it easier to identify if/when a driver is no longer
being maintained, allowing us to strike it off the list of "official
drivers" until it's been reined in.

I guess it depends on the level to which we want the drivers associated with


On 9 September 2011 15:21, Jonathan Ellis <> wrote:

> On Fri, Sep 9, 2011 at 8:40 AM, Rick Shaw <> wrote:
> > I worry that if the issue management is moved from the main JIRA for C*
> > sponsored drivers there will be synergy and awareness lost between client
> > and server. Did the Hector and Pelops folks see it as a good thing to
> have
> > their own?
> I can't speak for them, but I certainly see it as a good thing that
> Hector and Pelops and pycassa et al have their own trackers.  It's bad
> enough having JDBC tickets tagged "affects C* 0.8.4" when they are in
> the same tree, it makes even less sense when they are elsewhere.
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support

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