Hi Marco,
Great to hear that you put some thought into the topic. Judging from
the past we already tried once to support multiple external versions
within one connector (ElasticSearch) and it complicates things a lot.
So if it makes your development easier to create a different module
that should
Hi Martin,
I took a look at how other plugins have handled the migration and I have the
feeling most oped for a new connector (new module), instead of adding some
more packages to the existing one. Should I take the same route ?
The current connector builds a fat-jar that included version 3.0
Hi Marco,
Thanks for volunteering! It would be great if you could help with
contributions, they are much appreciated.
The plan is indeed to move connectors to its own individual repository, for
Cassandra that most likely would be something like
https://github.com/apache/flink-connector-cassandra.
Hi,
just discovered the voting thread and wanted to raise my hand to in an attempt
to maintain the Apache Cassandra connector. At work Kafka -> Flink ->
Cassandra is a very common usage pattern for me.
>From other ongoing threads I got that the connectors would be removed from
>main repositor
Hi everyone,
We're looking for community members, who would like to maintain Flink's
Cassandra connector [1] going forward. The connector currently is only
available as a Sink for DataStream users and the original contributors are
unable to work on further improvements.
An overview of some of the
