You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Rui Wang (Jira)" <ji...@apache.org> on 2019/09/10 22:04:00 UTC

[jira] [Closed] (BEAM-4193) [SQL] Support trigger definition in CLI

     [ https://issues.apache.org/jira/browse/BEAM-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rui Wang closed BEAM-4193.
--------------------------
    Fix Version/s: Not applicable
       Resolution: Won't Fix

Current plan is EMIT syntax to control output of SQL. So close this JIRA.

> [SQL] Support trigger definition in CLI
> ---------------------------------------
>
>                 Key: BEAM-4193
>                 URL: https://issues.apache.org/jira/browse/BEAM-4193
>             Project: Beam
>          Issue Type: New Feature
>          Components: dsl-sql
>            Reporter: Anton Kedin
>            Priority: Major
>             Fix For: Not applicable
>
>
> We need to be able to define triggers for the sources in SQL CLI. Otherwise it is impossible to reason about outputs.
> One approach is to come up with a simple JSON trigger definition syntax, along the lines of
>  
> {code:java}
> SET OPT( '{ "trgger" : { "DefaultTrigger" }, "allowedLateness" : 0 }' )
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)