[
https://issues.apache.org/jira/browse/FLINK-17916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17916:
-----------------------------------
Labels: auto-unassigned pull-request-available stale-major (was:
auto-unassigned pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Provide API to separate KafkaShuffle's Producer and Consumer to different jobs
> ------------------------------------------------------------------------------
>
> Key: FLINK-17916
> URL: https://issues.apache.org/jira/browse/FLINK-17916
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream, Connectors / Kafka
> Affects Versions: 1.11.0
> Reporter: Yuan Mei
> Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-major
> Fix For: 1.14.0
>
>
> Follow up of FLINK-15670
> *Separate sink (producer) and source (consumer) to different jobs*
> * In the same job, a sink and a source are recovered independently according
> to regional failover. However, they share the same checkpoint coordinator and
> correspondingly, share the same global checkpoint snapshot.
> * That says if the consumer fails, the producer can not commit written data
> because of two-phase commit set-up (the producer needs a checkpoint-complete
> signal to complete the second stage)
> * Same applies to the producer
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
