[
https://issues.apache.org/jira/browse/CASSSIDECAR-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080625#comment-18080625
]
Stefan Miklosovic commented on CASSSIDECAR-453:
-----------------------------------------------
https://github.com/apache/cassandra-sidecar/pull/344/changes/1c1a24b032504472f7ffed18ac6d0c83eeeab7fb
> CdcPublisher.eventConsumer uses static topic supplier - not possible to route
> events per TopicSupplier strategies
> -----------------------------------------------------------------------------------------------------------------
>
> Key: CASSSIDECAR-453
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-453
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: CDC
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There is {{TopicSupplier.staticTopicSupplier(conf.kafkaTopic()),}} in
> eventConsumer, that means that we can not route events to different topics,
> it always goes to the same.
> I have a pipeline from Cassandra to Clickhouse where I am doing 1:1 mapping
> (via transformers in Kafka Connector). So far it works just great when one
> table is involved, but I can not say that events from one table will go to
> one topic and events from another can go to another topic. Then I can have a
> connector per topic, do the transformations and put data to respective
> Clickhouse table.
> It seems to me that this is already there, it is just not used.
> Sorry if this is a duplicate.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
