[
https://issues.apache.org/jira/browse/FLINK-22748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355098#comment-17355098
]
Nicholas Jiang edited comment on FLINK-22748 at 6/1/21, 1:34 PM:
-----------------------------------------------------------------
IMO, as [~twalthr] mentioned, the solution that use `WritableMetadata` makes
sense. The config option for the dynamic target topic is less reasonable than
writable metadata columns. The writable topic could be included in metadata
columns.
[~jark], which solution do you prefer?
was (Author: nicholasjiang):
IMO, as [~twalthr] mentioned, the solution that use `WritableMetadata` makes
sense. The config option for the dynamic target topic is less reasonable than
writable metadata columns. The writable topic could be included in metadata
columns.
> Allow dynamic target topic selection in SQL Kafka sinks
> -------------------------------------------------------
>
> Key: FLINK-22748
> URL: https://issues.apache.org/jira/browse/FLINK-22748
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka, Table SQL / Ecosystem
> Reporter: Timo Walther
> Priority: Major
> Labels: starter
>
> We should allow to write to different Kafka topics based on some column value
> in SQL.
> The existing implementation can be easily adapted for that. The "target
> topic" would be an additional persisted metadata column in SQL terms. All one
> need to do is to adapt
> DynamicKafkaSerializationSchema
> KafkaDynamicSink
> We should guard this dynamic behavior via a config option and make the topic
> option optional in this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
