Piotr Grabowski

> > that way it will be consistent with our another connector: `scylla-cdc-source-connector` > > Btw, I really don't like Uppercase character in the name of scylla-cdc-source-connector. It should be...

@sylwiaszunejko is currently working on this issue: https://github.com/scylladb/python-driver/issues/295 which seemed more current (before issues reported by @piodul today). I'll try to get to this soon.

> However, it brings me to the question, do we really want to run the CI with the parameter of fetching the OSS RC releases? The original rationale was to...

@Lorak-mmk thoughts?

As @Gor027 mentioned, the tests targets are using Maven for running tests. This works correctly, but isn't super well integrated with IntelliJ. Moreover, it's hard to run such target in...

In new Replicator integration tests, this is tested here: https://github.com/scylladb/scylla-cdc-java/blob/ca2949a477cf7dba42ad2872933dc5f906435f37/scylla-cdc-replicator/src/test/java/com/scylladb/cdc/replicator/ReplicatorCorrectnessTestIT.java#L388-L418 (should be uncommented if this issue is fixed)

This is fixed by setting larger -clustering-row-size

This error in integration tests looks a bit worrying: ``` com.datastax.oss.driver.api.core.AllNodesFailedException: Could not reach any contact point, make sure you've provided valid addresses (showing first 1 nodes, use getAllErrors() for...

> Note, we should adopt a waterfall procedure. First apply fixes/features on the main branch, then selectively backport to branches. > > Starting with the older branch means that there...

I should better document this organization and clean up unrelated branches (remnants of upstream Datastax repo)