[
https://issues.apache.org/jira/browse/CALCITE-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170140#comment-17170140
]
Rui Wang commented on CALCITE-4146:
-----------------------------------
Also, there are also three output mode for EMIT
1. discarding/delta mode. This is like a macro batch system.
2. accumulating mode. This is each emit of the batch all contains all history
data.
3. accumulating and discarding mode. This is the one that retractions will
exist.
in Calcite, EMIT syntax will work with 3. I haven't had an idea whether to
support 1 and 2.
> 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)
