[
https://issues.apache.org/jira/browse/FLINK-18578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-18578:
-----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
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.
> Add rejecting checkpoint logic in source
> ----------------------------------------
>
> Key: FLINK-18578
> URL: https://issues.apache.org/jira/browse/FLINK-18578
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / Common, Runtime / Checkpointing
> Reporter: Qingsheng Ren
> Priority: Major
> Labels: auto-unassigned, stale-major
>
> Under some database's change data capture (CDC) case, the process is usually
> divided into two phases: snapshotting phase (lock captured tables and scan
> all records in them) and log streaming phase (read all changes starting from
> the moment of locking tables) in order to build a complete view of captured
> tables. The first snapshotting phase should be atomic so we have to give up
> all records created in snapshotting phase if any failure happen, because
> contents in captured tables might have changed during recovery. And
> checkpointing within snapshotting phase is meaningless too.
> As a result, we need to add a new feature in the source to reject checkpoint
> if the source is currently within an atomic operation or some other processes
> that cannot do a checkpoint currently. This rejection should not be treated
> as a failure that could lead to failure of the entire job.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
