[
https://issues.apache.org/jira/browse/FLINK-24493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023865#comment-18023865
]
Rion Williams commented on FLINK-24493:
---------------------------------------
[~fpaul] / [~arvid]
I was considering knocking a bit of dust off of this effort as it relates to
some work that I recently did (migrating similar implementation to the new
Unified Sink API) for a handful of older Flink jobs. This got me thinking about
revisiting this effort to support the multiplexing behavior described earlier
within this thread.
I wasn't sure how to best go about targeting the implementation, so I thought
I'd ask you both. Would it be best to target something like this in Flink 2.0
and backport it to the Flink 1.x branch? Obviously I haven't started on the
implementation of this yet, but wanted to ask prior to doing anything.
Much appreciated!
Rion
> Introduce DemultiplexingSink to Support Dynamic Sink Routing
> ------------------------------------------------------------
>
> Key: FLINK-24493
> URL: https://issues.apache.org/jira/browse/FLINK-24493
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / Common
> Reporter: Rion Williams
> Assignee: Rion Williams
> Priority: Major
>
> Recently, FLINK-23977 attempted to introduce an approach to supporting
> dynamic routing for the Elasticsearch sink, however during some discussion
> within [the pull request|https://github.com/apache/flink/pull/17061], the
> idea was introduced to create a more generic approach.
> The idea being that we could introduce a common DemultiplexingSink and
> related interface for handling routing to any number of existing sinks
> similar to the implementation mentioned in FLINK-23977 to the common
> connectors directory.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
