[
https://issues.apache.org/jira/browse/FLINK-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571638#comment-14571638
]
ASF GitHub Bot commented on FLINK-2098:
---------------------------------------
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/742#issuecomment-108615858
I thought about what @StephanEwen said about uncheckpointed sources also
having the locking object in the signature of the run() method and also about
extensibility.
We might have to tweak the source interface a little bit more. What I
propose is to have this run method:
```
void run(SourceContext context);
```
Then the source context would have methods to retrieve the locking object
(for checkpointed sources) and for emitting elements. Part of my motivation for
this is that this can be extended in the future without breaking existing
sources. If we introduce proper timestamps at some point we can extend the
SourceContext with a method for emitting elements with a timestamp. Then, if we
want to have watermarks the context can have methods for activating
automatically generated watermarks and for emitting watermarks. And so on...
I think we should fix this now, before the release. What do you think?
> Checkpoint barrier initiation at source is not aligned with snapshotting
> ------------------------------------------------------------------------
>
> Key: FLINK-2098
> URL: https://issues.apache.org/jira/browse/FLINK-2098
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 0.9
> Reporter: Stephan Ewen
> Assignee: Aljoscha Krettek
> Priority: Blocker
> Fix For: 0.9
>
>
> The stream source does not properly align the emission of checkpoint barriers
> with the drawing of snapshots.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
