# SQL Debezium source to topic to JDBC sink target

**URL:** <https://forum.confluent.io/t/sql-debezium-source-to-topic-to-jdbc-sink-target/4140>\
**Category:** Managed Connectors\
**Created:** [10 February 2022 18:27 UTC](https://forum.confluent.io/t/sql-debezium-source-to-topic-to-jdbc-sink-target/4140 "2022-02-10T18:27:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![whatsupbros](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/whatsupbros/32/239_2.png) [@whatsupbros](https://forum.confluent.io/u/whatsupbros)\
**Post date:** [11 February 2022 15:40 UTC](https://forum.confluent.io/t/sql-debezium-source-to-topic-to-jdbc-sink-target/4140/4 "2022-02-11T15:40:19Z")

</div>

Well, it is up to you when to apply the unwrapping, but enveloping of the data was implemented there for a reason actually, so I would recommend using it on the Sink connector side.

As of `fields.blacklist` - sorry for the confusion, what I meant was actually [ReplaceField SMT](https://docs.confluent.io/platform/current/connect/transforms/replacefield.html), which allows you to whitelist or [blacklist](https://docs.confluent.io/platform/current/connect/transforms/replacefield.html#drop-a-field) the fields…

---

_[View the full topic](https://forum.confluent.io/t/sql-debezium-source-to-topic-to-jdbc-sink-target/4140)._