If it's helpful, IMO, the approach Cassandra needs to take isn't by tracking the individual node commit log and putting the burden on the client. At Scylla, we had the 'opportunity' to be a late comer and see what approach Cassadnra took and what DynamoDB streams took.
We've implemented CDC as a regular CQL table [1]. Not only it's super easy to consume, it's also consistent and you can choose to read the older values. I recommend Cassandra should pick up our design, a small contribution back. We're implementing an OSS kafka CDCk connector too. Dor [1] https://www.scylladb.com/2020/03/31/observing-data-changes-with-change-data-capture-cdc/ On Wed, May 27, 2020 at 5:41 PM Erick Ramirez <erick.rami...@datastax.com> wrote: > I have looked at DataStax CDC but I think it works only for DSE ! >> > > Yes, thanks for the correction. I just got confirmation myself -- the > Kafka-Cassandra connector works with OSS C* but the CDC connector relies on > a DSE feature that's not yet available in OSS C*. Cheers! >
