-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Upgrade Cassandra driver to 4.x #2768
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this. |
Please don't close this. There is a PR for this issue: #2830. |
This issue has been automatically closed due to inactivity. We apologise if this is still an active problem for you, and would ask you to re-open the issue if this is the case. |
Reopening, and labelling so that it won't be closed automatically. |
A new implementation has been added in #8616 and it doesn't rely on the cassandra client. |
Currently, the CassandraContainer makes use of the DataStax 3.7.1 driver. The 3.x series of the driver is effectively in maintenance mode and only receiving critical fixes.
The 4.x driver series has been released for a while, with the current latest version being 4.6.1, however, the new driver is not a drop-in binary compatible replacement.
I would be happy to post a PR to upgrade the driver, if acceptable.
The text was updated successfully, but these errors were encountered: