# Transactional consistency using Kafka Connect

**URL:** <https://forum.confluent.io/t/transactional-consistency-using-kafka-connect/10718>\
**Category:** Kafka Connect\
**Created:** [20 May 2024 09:43 UTC](https://forum.confluent.io/t/transactional-consistency-using-kafka-connect/10718 "2024-05-20T09:43:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![abc](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@abc](https://forum.confluent.io/u/abc)\
**Post date:** [20 May 2024 09:43 UTC](https://forum.confluent.io/t/transactional-consistency-using-kafka-connect/10718/1 "2024-05-20T09:43:22Z")

</div>

We are using Kafka Connect, Oracle CDC Source Connector, to create multiple table-specific topics.

If a change is made to multiple tables in a single transaction in Oracle DB, is there a way to then ensure that these changes are only consumed/joined as a single stream safely (using Kafka Streams or ksqlDB).

This is to ensure that the joined stream will never represent a state that didn’t exist in Oracle DB.

Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/confluentcommunity/original/1X/c49438c90c9df282e9996fdf6971be890c71b65a.svg) [@system](https://forum.confluent.io/u/system)\
**Post date:** [19 June 2024 09:43 UTC](https://forum.confluent.io/t/transactional-consistency-using-kafka-connect/10718/2 "2024-06-19T09:43:29Z")

</div>

Closed on 19 June 2024 09:43 UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.