[
https://issues.apache.org/jira/browse/FLINK-15670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019222#comment-17019222
]
Yuan Mei edited comment on FLINK-15670 at 1/20/20 6:15 AM:
-----------------------------------------------------------
I like this idea.
If my understanding correctly, we provide predefined Kafka `keyed and avoid
repartition` source/sink pair; users are responsible to create Kafka topic and
connect the source to the sink through DataStream API.
Is this solution general/feasible for SQL as well?
was (Author: ym):
I like this idea.
If understanding correctly, we provide predefined Kafka `keyed and avoid
repartition` source/sink pair; users are responsible to create Kafka topic and
connect the source to the sink through DataStream API.
Is this solution general/feasible for SQL as well?
> Provide a Kafka Source/Sink pair that aligns Kafka's Partitions and Flink's
> KeyGroups
> -------------------------------------------------------------------------------------
>
> Key: FLINK-15670
> URL: https://issues.apache.org/jira/browse/FLINK-15670
> Project: Flink
> Issue Type: New Feature
> Components: API / DataStream, Connectors / Kafka
> Reporter: Stephan Ewen
> Priority: Major
> Labels: usability
> Fix For: 1.11.0
>
>
> This Source/Sink pair would serve two purposes:
> 1. You can read topics that are already partitioned by key and process them
> without partitioning them again (avoid shuffles)
> 2. You can use this to shuffle through Kafka, thereby decomposing the job
> into smaller jobs and independent pipelined regions that fail over
> independently.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
