[
https://issues.apache.org/jira/browse/CASSANDRA-18998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788561#comment-17788561
]
Stefen Hillman commented on CASSANDRA-18998:
--------------------------------------------
I'm not familiar with that work. Sounds like this almost made it in? Is there
plan to fully implement this any time in the near future? How much work will
that take?
> 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
> Assignee: Dinesh Joshi
> 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: [email protected]
For additional commands, e-mail: [email protected]
