[
https://issues.apache.org/jira/browse/FLINK-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321649#comment-17321649
]
Flink Jira Bot commented on FLINK-6947:
---------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> Warn user when assigning timestamps/watermarks after a union
> ------------------------------------------------------------
>
> Key: FLINK-6947
> URL: https://issues.apache.org/jira/browse/FLINK-6947
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Affects Versions: 1.2.1, 1.3.0
> Reporter: Petr Novotnik
> Priority: Minor
> Labels: stale-minor
>
> Placing timestamp assignment (and watermark generation) directly or
> indirectly after a union is generally not desirable as it may lead to
> surprising results at the client side. Ideally, timestamp assignment (and
> watermark generation) is best placed as close as possible to the data
> sources. It would be nice to generate a warning to the user (i.e. to the
> log) before job execution if the framework detects timestamp assignment
> (directly or indirectly placed) after a union.
> Some more background information for this issue can be found in this email
> thread:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/union-followed-by-timestamp-assignment-watermark-generation-td13036.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
