Cassandra Socks5 Proxy options #131
Conversation
|
Hello folks @adutra @tomekl007 @absurdfarce @stamhankar999 @eolivelli any chance I could get some help getting this change over the line? This PR relies on merging/releasing a change I have proposed (and provided a link to above) for the Datastax/java-driver repo so reviewing that PR would be a pre-recquisite. Thanks in advance 🙂 |
|
LGTM We should do the same change in datastax/pulsar-sink that is basically the same connector but for Pulsar. would you mind sending the patch also to pulsar-sink when you are done with the Driver ? |
|
if you want to cut a release of this project we can try to do it together |
|
Hi @eolivelli , thanks for the response. Would you be able to help us in getting the Java-Driver PR approved and released? (apache/cassandra-java-driver#1584) The Java-Driver PR has been open for a while - once it's released we will be unblocked and able to proceed with this PR. |
I have a requirement to get a number of applications/services to route their Cassandra traffic through a Socks5 proxy layer.
This has proven to be an easy task for many of these services as they make use of the com.datastax.driver.core.Cluster library - which exposes methods such as Cluster.withNettyOptions() which makes routing Cassandra traffic through a proxy possible, following this community blog post: https://community.datastax.com/questions/851/connection-to-a-cluster-via-a-socks-proxy.html
However, my instance of Kafka-Connect uses the Datastax/Kafka-Sink library (which consumes this Java-Driver library under the hood) - which sadly does not expose any way to route Cassandra traffic through a Socks 5 proxy. This PR is an attempt to inner source and implement this feature.
The accompanying Java-Driver PR to this change is as follows: apache/cassandra-java-driver#1584
TODO Note: This Kafka-Sink change requires the Java-Driver PR to be reviewed/merged/published first, and then the subsequent latest version of Java Driver is to be consumed in the pom.xml file for this repo.