[ https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385188#comment-17385188 ]
Aitozi edited comment on FLINK-23031 at 7/22/21, 2:02 AM: ---------------------------------------------------------- Hi [~jark] , after some offline discussion with you. I rethink this improvement can be describe in this way: It's add a "trigger-after-changed" semantic to early/late fire phase. So can we add options below. {code:java} table.exec.emit.late-fire.trigger-after-changed.enabled table.exec.emit.early-fire.trigger-after-changed.enabled {code} And the default behavior to keep compatible with now. If user want to skip redundant/"no-change" timer,can use this "trigger-after-changed" semantic be set to true. Looking forward to your opinion. 3Q. was (Author: aitozi): Hi [~jark] , after some offline discussion with you. I rethink this improvement can be describe in this way: It's add a "trigger-after-changed" semantic to early/late fire phase. So can we add options below. {code:java} table.exec.emit.late-fire.trigger-after-changed.enabled table.exec.emit.early-fire.trigger-after-changed.enabled {code} And the default behavior to keep compatible with now. If user want to skip redundant/"no-change" timer,can use this "trigger-after-changed" semantic be set to true. Looking forward to your opinion. 3Q. > Support to emit window result with periodic or non_periodic > ----------------------------------------------------------- > > Key: FLINK-23031 > URL: https://issues.apache.org/jira/browse/FLINK-23031 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner > Reporter: Aitozi > Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)