Closed avelanarius closed 1 year ago
Scylla CI with this branch of scylla-tools-java passed successfully: https://github.com/scylladb/scylladb/pull/12094
(Changing to draft for a second, will bump it to 3.11.2.4 which will have https://github.com/scylladb/java-driver/commit/22e3ad5dc0de4cea8fe45370ff6fa4650c4bafd1)
v2: Update to 3.11.2.4 (v1 of PR was update to 3.11.2.3)
Ran CI tests again and they passed correctly: https://github.com/scylladb/scylladb/pull/12094
ping @avikivity for review and merge
@nyh is there a github group of the core maintainers that we can ping ? inside of picking up on specific ones that might be busy, i.e. like @avikivity ?
I don't know, but I'll take it as a hint and review this patch myself :-)
I don't know, but I'll take it as a hint and review this patch myself :-)
Thanks @nyh, I was waiting for the fixes in this for a couple of weeks.
Yes, our review process is famous for its speed ;-)
@nyh is there a github group of the core maintainers that we can ping ? inside of picking up on specific ones that might be busy, i.e. like @avikivity ?
@scylladb/scylla-maint
Update the version of Java Driver from 3.11.2.1 to 3.11.2.4. The differences between the versions are fixes to serverless support:
Without this change, cassandra-stress could not connect correctly to a local serverless cluster created with Scylla Operator or CCM (see https://github.com/scylladb/java-driver/issues/164).
Tested manually end-to-end scenario: starting serverless Scylla with CCM and using cassandra-stress to write to it: