You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Rui Wang (Jira)" <ji...@apache.org> on 2020/08/06 17:24:01 UTC
[jira] [Commented] (CALCITE-4164) Create a Spec doc for EMIT syntax
[ https://issues.apache.org/jira/browse/CALCITE-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172561#comment-17172561 ]
Rui Wang commented on CALCITE-4164:
-----------------------------------
This JIRA blocks other implementation tasks.
> Create a Spec doc for EMIT syntax
> ---------------------------------
>
> Key: CALCITE-4164
> URL: https://issues.apache.org/jira/browse/CALCITE-4164
> Project: Calcite
> Issue Type: Sub-task
> Reporter: Rui Wang
> Assignee: Rui Wang
> Priority: Major
>
> Basically have a spec doc to introduce EMIT from SQL language/relation algebra perspective. This is very important because EMIT syntax is non-standard (maybe not yet) so it becomes an extension that Calcite introduces.
> The format might be as strict and detailed as what SQL standard does, but at least in should include:
> 1. new SQL syntax
> 2. new SQL keywords
> 3. The scope of EMIT clause (might not be needed as we won't allow column appear in EMIT clause)
> 4. All EMIT strategies
> 5. How does EMIT strategies propagate through the plan.
> For 5 my current thought it is EMIT will just affect FROM clause. For non-stream case it just means data emit all at once (e.g. EMIT AFTER WATERMARK).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)