-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supporting Cassandra 3.0+ #612
Comments
@uluyol - thanks for checking the compatibility on this. Are you interested in submitting a PR to update the driver? |
I've successfully added a |
there's already a PR open (#614) that updates cassandra2-cql to use the 3.x driver (which should be able to work with all the relevant versions). I believe that PR is just waiting for @uluyol to fix an error in the test cases. If you'd like to start from that PR and add a commit that fixes the tests, that'd be the fastest way to get Cassandra 3.x support merged. |
The test case error is due to cassandra and cassandraunit version conflict. The latest cassandraunit release is 2.2.2.1. After run command "mvn clean package -DskipTests", it works just fine with 3.X version. |
great! that sounds like an easy enough fix. If you'd like to start from that PR and add a commit that fixes the tests, that'd be the fastest way to get Cassandra 3.x support merged. |
I pulled down #614 and updated cassandra unit to 2.2.2.1 and that didn't fix the test errors. Same error with signature mismatch basically. Looks like cassandraunit isn't at 3.x yet so doesn't support the 3.x classes? I don't know if there is an easy way to fix this yet. |
True, current Cassandra unit doesn't support 3.x version yet. I have to manually bypass test to build the project to make it work with 3.x Cassandra cluster. |
The current cassandra2-cql layer errors when used with new versions of cassandra.
Updating the version of the cassandra driver to 3.0.0 fixes this. As per http://datastax.github.io/java-driver/#compatibility, compatibility with older versions should be unaffected.
The text was updated successfully, but these errors were encountered: