[
https://issues.apache.org/jira/browse/CASSANDRA-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082668#comment-13082668
]
Eric Evans commented on CASSANDRA-2761:
---------------------------------------
bq. Then you're not very familiar with the current stability or lack there of
of the JDBC driver.
No, I guess not, but it can't be any worse on us than for anyone else using it.
A solution that only benefits us doesn't seem very... friendly.
----
I think the difference in opinion here comes from what determines whether the
server and driver should be considered different projects. I can see where
people who feel a high degree of ownership over the code of both, and who by
virtue of infrastructure have write access to both, might consider it contrived
to treat them as separate projects. I'm not discounting that point of view,
but I do think that's more Social than Technical, and is limited to a
relatively small group of Cassandra hackers.
As I've said elsewhere, I think it is very important that these drivers be
allowed to evolve on their own release schedule with their own versioning that
reflects compatibility with a CQL version and not any particular Cassandra
version(s). It's also quite likely, particularly where the driver language !=
Java that the group of developers is entirely different from those working on
the server. And there is no hard dependency between drivers and Cassandra in
either direction (the JDBC->Cassandra dependency is one of convenience). To
me, this pretty solidly points to them being separate projects.
Keeping them separate won't be as convenient as treating them as one monolithic
project, but it's no worse an experience than what other application developers
are subjected to. We should be able to eat our own dog food.
I also realize that there is more work needed here to decouple the JDBC driver
and make this all work better, work that I've volunteered to do. I haven't had
as much time to spend on this lately, but that should be changing RSN.
> JDBC driver does not build
> --------------------------
>
> Key: CASSANDRA-2761
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2761
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 1.0
> Reporter: Jonathan Ellis
> Assignee: Rick Shaw
> Fix For: 1.0
>
> Attachments: jdbc-driver-build-v1.txt,
> v1-0001-CASSANDRA-2761-cleanup-nits.txt
>
>
> Need a way to build (and run tests for) the Java driver.
> Also: still some vestigal references to drivers/ in trunk build.xml.
> Should we remove drivers/ from the 0.8 branch as well?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
