You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2023/11/03 21:07:00 UTC

[jira] (CASSANDRA-18998) Expose CDC via CQL

    [ https://issues.apache.org/jira/browse/CASSANDRA-18998 ]


    Stefan Miklosovic deleted comment on CASSANDRA-18998:
    -----------------------------------------------

was (Author: smiklosovic):
Have you tried this? https://github.com/debezium/debezium-connector-cassandra

> Expose CDC via CQL
> ------------------
>
>                 Key: CASSANDRA-18998
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18998
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Feature/Change Data Capture
>            Reporter: Stefen Hillman
>            Priority: Normal
>
> It looks like there was originally a plan to expose change data externally via CQL for any client to consume, as noted under Design Options #4 on the original design document: [https://docs.google.com/document/d/1ZxCWYkeZTquxsvf5hdPc0fiUnUHna8POvgt6TIzML4Y/edit?usp=sharing.]
>  
> It appears that this was ultimately not implemented. Is there a plan to improve CDC in the future with this functionality? The current implementation is tedious to use - you have to write a local agent that lives on every single c* node and then implement the Apache-provided CommitLogReader in order to parse the files. On top of that, it makes deduplication and ordering basically impossible if there isn't an inherently ordered property.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org