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

Julian Hyde commented on CALCITE-4146:
--------------------------------------

[~amaliujia], Implementing EMIT in its entirety involves a lot of small tasks. 
Can you manage this process by creating a Jira case to hold everything? I don't 
mind if each task is focused on something small (e.g. EMIT AFTER WATERMARK for 
non-join queries and HOP/SESSION table functions) as somewhere we track what is 
left.

Another task is to update 
[reference.md|https://calcite.apache.org/docs/reference.html] and 
[stream.md|https://calcite.apache.org/docs/stream.html].

We should have a syntax to request classic SQL semantics, something like {{EMIT 
WHEN COMPLETE}}.

> 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 [One SQL to Rule Them 
> All|https://arxiv.org/pdf/1905.12133.pdf]. 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 
> [CALCITE-3272|https://issues.apache.org/jira/browse/CALCITE-3272?focusedCommentId=17166580&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17166580]
>  and the [EMIT syntax proposal for event-timestamp semantic 
> windowing|https://lists.apache.org/thread.html/r5bd9a6f7af2c0cd81aecd4de512fd889fbf15f112cc3704f188b1d4f%40%3Cdev.calcite.apache.org%3E]
>  email thread.



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

Reply via email to