'Difference between JDBC Sink Connector vs Redshift Sink Connector
I'm new to Kafka and I would like to know why there are specific Database connectors like Redshift Sink Connector and why we should not go for generic JDBC sink connectors. What are the advantages or differences between both.
Also, the Redshift Sink connector is giving me poor performance. Is there anyway to improve the same?
Solution 1:[1]
why there are specific Database connectors like Redshift Sink Connector
Because there is a Java AWS SDK written for Redshift, and this is what that connector uses.
The JDBC Sink connector has no hard-dependency on the AWS SDK
why we should not go for generic JDBC sink connectors
Ideally, you don't want to expose your AWS credentials in the Connect API configurations, I assume.
Also, the Redshift JDBC "dialect" might not be supported by the Confluent Connector
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | OneCricketeer |