flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7564) Fix Watermark semantics in Table API
Date Tue, 05 Sep 2017 09:12:01 GMT

    [ https://issues.apache.org/jira/browse/FLINK-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153334#comment-16153334

ASF GitHub Bot commented on FLINK-7564:

Github user xccui commented on the issue:

    Thanks for the review, @fhueske. I tried to consolidate the logics for proctime and rowtime
watermark processing, but failed. That's because when using proctime, the "watermark" (not
sure if this concept exists for proctime) for triggering the timers is set to be identical
with the current record's processing time, thus all the records will be considered late. Do
you think it's necessary to unify their behaviors, or we just take the proctime as a special

> Fix Watermark semantics in Table API
> ------------------------------------
>                 Key: FLINK-7564
>                 URL: https://issues.apache.org/jira/browse/FLINK-7564
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API & SQL
>            Reporter: Aljoscha Krettek
>            Assignee: Xingcan Cui
>            Priority: Blocker
>             Fix For: 1.4.0, 1.3.3
> For reference, see https://lists.apache.org/thread.html/3541e72ba3842192e58a487e54c2817f6b2b9d12af5fee97af83e5df@%3Cdev.flink.apache.org%3E.

This message was sent by Atlassian JIRA

View raw message