[
https://issues.apache.org/jira/browse/FLINK-16868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071020#comment-17071020
]
Jark Wu commented on FLINK-16868:
---------------------------------
As far as I can tell, the community don't have a plan to support custom
triggers, because triggers are not suitable in SQL concepts. But blink planner
already provides a similar experimental feature called emit strategy, it can be
enabled by global configurations {{TableConfig.getConfiguration()}}.
{code:java}
table.exec.emit.early-fire.enabled=true
table.exec.emit.early-fire.delay=3s
table.exec.emit.late-fire.enabled=true
table.exec.emit.late-fire.delay=5s
{code}
> Table/SQL doesn't support custom trigger
> ----------------------------------------
>
> Key: FLINK-16868
> URL: https://issues.apache.org/jira/browse/FLINK-16868
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API, Table SQL / Runtime
> Reporter: Jimmy Wong
> Priority: Major
> Fix For: 1.9.0, 1.9.1, 1.9.2
>
>
> Table/SQL doesn't support custom trigger, such as CountTrigger,
> ContinuousEventTimeTrigger/ContinuousProcessingTimeTrigger. Do we has plans
> to make it?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
