You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Anton Kedin (JIRA)" <ji...@apache.org> on 2018/04/30 18:07:00 UTC
[jira] [Updated] (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 ]
Anton Kedin updated BEAM-4193:
------------------------------
Description:
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}
was:
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
SET OPT( '\{ "trgger" : { "DefaultTrigger" }, "allowedLateness" : 0 }' )
> [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
>
> 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
(v7.6.3#76005)