Hello Martijn, Thanks a lot for the answer. Other question I have if you could help me.
Is there a proper way to define sequential sinks? Meaning if we could have a sequence of sinks that operate in order instead of operating in parallel Best regards, Carlos Freitas > On 23 Jan 2023, at 12:52, Martijn Visser <martijnvis...@apache.org> wrote: > > Hi Carlos, > > Yes, the new Sink interface is ultimately the target for all Sink > connectors. A discussion on that topic has started recently, which you can > see at https://lists.apache.org/thread/q62nj89rrz0t5xtggy5n65on95f2rmmx. > Currently Kafka, Elasticsearch, Opensearch, Kinesis, Firehose, DynamoDB and > more are already using the new interface. JDBC doesn't yet, but there is a > PR open for that https://github.com/apache/flink-connector-jdbc/pull/2. > > For context on why a new Sink interface was created, I would recommend > checking out FLIP-143 that talked about this. You can find that at > https://cwiki.apache.org/confluence/display/FLINK/FLIP-143%3A+Unified+Sink+API > > Best regards, > > Martijn > > Op ma 23 jan. 2023 om 13:35 schreef Carlos Freitas > <carlos.frei...@talkdesk.com.invalid>: > >> Hello everyone, >> >> I have a question more on the curiosity side, unsure if this has been >> discussed before (sorry if It has). Given the recent deprecation of the >> `FlinkKafkaProducer` in favour of the new `KafkaSink` where we get away >> from the `SinkFunction` interface in favour of the “new” `Sink` interface. >> My question here is if there is any plan on making a similar move in any >> other sink (eg. JDBC connector sink) either by using the same Sink >> interface that Kafka uses or any other one that does not make direct use of >> SinkFunction anymore. >> >> PS. I do not have the context on why was decided to deprecate >> FlinkKafkaProducer in the first place. >> >> Cumps, >> Carlos Freitas
