Wojciech Bączkowski
Wojciech Bączkowski
Tested manually and driver part was additionally tested using unit test included in [scylladb/scylla-cdc-java/75](https://github.com/scylladb/scylla-cdc-java/pull/75)
Hi, this can be solved by setting `scylladb.offset.storage.table=another_table`. This way connectors won't clash with each other if you need to store offsets on Scylla. While not having to modify default...
No issues observed when running with LZ4, Deflate, Snappy and no table compression. No issues observed with Snappy protocol compression.
Hi, I'm not really familiar with Kotlin, but I tried replicating this. It seems to me this problem is related to the bug with default interface methods [(KT-4779)](https://youtrack.jetbrains.com/issue/KT-4779) and what...
Currently I've made almost complete switch to the solution that uses custom payloads instead of querying system.tablets. I've ran some tests on local 4 node cluster and so far there...
Currently it's waiting for review. I've done some manual testing, but haven't done any stress testing under heavy load.
Will do. At first i thought 2024.1.2 failures were a one off, since it looked liked there's a lot of similar test errors relating to starting the cluster (and only...
I believe this is due to driver calculating connections per shard (while PoolingOptions limits are per host). If the limit is not evenly divisible by the number of shards, driver...
This should be passing now (or with the new version release), since #210 was merged. I've settled on the same workaround but without duplicating tests.