[jira] [Comment Edited] (CALCITE-4146) Implement EMIT AFTER WATERMARK

["Rui Wang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169699#comment-17169699 ] 

Rui Wang edited comment on CALCITE-4146 at 8/3/20, 3:48 AM:
------------------------------------------------------------

BTW, in Apache Beam and Google Cloud Dataflow, window is just window, there are no count/time windows. By doing so it still works pretty well.


was (Author: amaliujia):
BTW, in Apache Beam and Google Cloud Dataflow, window are just window, there are not count/time windows. By doing so it still works pretty well.

> Implement EMIT AFTER WATERMARK
> ------------------------------
>
>                 Key: CALCITE-4146
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4146
>             Project: Calcite
>          Issue Type: Sub-task
>            Reporter: Rui Wang
>            Assignee: Rui Wang
>            Priority: Major
>
> The goal is to support the following syntax
> {code:sql}
> SELECT clause
> FROM TUMBLE/HOP/SESSION
> EMIT AFTER WATERMARK
> {code}
> note that "EMIT AFTER WATERMARK" is the new thing.
> "EMIT AFTER WATERMARK" is proposed in [1]. This idea proposes a way to allow streaming SQL queries control materialization latency. More specifically, it means emit elements in a window once the watermark passes the end of that window.
> There are more context discussed in [2][3].
> [1]: https://arxiv.org/pdf/1905.12133.pdf
> [2]: https://issues.apache.org/jira/browse/CALCITE-3272?focusedCommentId=17166580&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17166580
> [3]:https://lists.apache.org/thread.html/r5bd9a6f7af2c0cd81aecd4de512fd889fbf15f112cc3704f188b1d4f%40%3Cdev.calcite.apache.org%3E



--
This message was sent by Atlassian Jira
(v8.3.4#803005)