incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Jackson <robe...@promedicalinc.com>
Subject Re: Proposal: Moving CQL drivers
Date Tue, 06 Sep 2011 17:37:22 GMT
This looks like a good plan. 


Once the drivers are moved to Google Code, would we be managing/tracking issues via Google
Code or still via JIRA? I would assume Google Code, but wanted to clarify. 

Since each driver will likely be in it's own repository I would also like to see the ruby
driver [1] migrated as well. It doesn't necessarily make sense to merge it into the main C*
tree just to move it out, and it does appear ready for publishing to me. At this point it
is fully functional, and performs as well or better than the thrift-api based fauna/cassandra
on some simple tests I performed [2]. 

[1] - https://issues.apache.org/jira/browse/CASSANDRA-2500 
[2] - https://gist.github.com/1185026 

Robert Jackson 



----- Original Message -----

From: "Eric Evans" <eevans@acunu.com> 
To: dev@cassandra.apache.org 
Sent: Tuesday, September 6, 2011 1:20:59 PM 
Subject: Proposal: Moving CQL drivers 

So following on from the previous discussion[1] about moving the CQL 
drivers out of tree, my interpretation of that discussion is that we 
have consensus that this should be done, and that they should go in 
Google Code and Apache Extras. Further, it seems a foregone 
conclusion that Git be used, and so I also assume that's a safe 
assumption, at least for the two existing drivers (Python and Java). 

One of the obstacles was the tight coupling of components that the 
JDBC driver depends on, which should now be solved in trunk 
(https://issues.apache.org/jira/browse/CASSANDRA-2936). Other than 
that the only items remaining relate to updating the tests so that 
they can connect to an already running instance, instead of the 
setup/teardown of nodes that is done now. 

Here is what I propose to do (one driver at a time): 

1. Setup new Git-based projects on Apache Extras (cassandra-jdbc and 
cassandra-dbapi2) 
2. Import the most current code and fix-up the tests as needed 
3. Submit issues w/ patches for the removal of the corresponding 
driver from Cassandra 

I would like to have this in place for 1.0, and believe it should be 
OK despite the fact that we are freezing on September 8 (we're still 
freezing on 9/8 I assume?). Since the plan was to delete the drivers 
directory after branching anyway, this shouldn't be disruptive to the 
release (even if drivers/ weren't deleted, the only functional change 
would be to remove JDBC build and test targets from build.xml). 

Thoughts? 


[1]: http://thread.gmane.org/gmane.comp.db.cassandra.devel/4075 

-- 
Eric Evans 
Acunu | http://www.acunu.com | @acunu 


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