[
https://issues.apache.org/jira/browse/FLINK-22133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342063#comment-17342063
]
Thomas Weise commented on FLINK-22133:
--------------------------------------
Hi Becket, I think the suggestion from Stephan would be the best approach. It
doesn't break existing users and at the same time allows to build
customizations in a 1.13 compatible manner.
PublicEvolving should not be modified in binary incompatible way between patch
releases and the japicmp check guards that. So if we were to make the same
change as in 1.13, we would require an exclusion. But I think we better stick
with the compatibility guarantee.
> SplitEmumerator does not provide checkpoint id in snapshot
> ----------------------------------------------------------
>
> Key: FLINK-22133
> URL: https://issues.apache.org/jira/browse/FLINK-22133
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Common
> Affects Versions: 1.12.0
> Reporter: Brian Zhou
> Assignee: Stephan Ewen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
> In ExternallyInducedSource API, the checkpoint trigger exposes the checkpoint
> Id for the external client to identify the checkpoint. However, in the
> FLIP-27 source, the SplitEmumerator::snapshot() is a no-arg method. The
> connector cannot track the checkpoint ID from Flink
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
