[
https://issues.apache.org/jira/browse/FLINK-18686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164026#comment-17164026
]
hailong wang edited comment on FLINK-18686 at 7/23/20, 11:38 PM:
-----------------------------------------------------------------
In my business, I want to compute the PV from zero to the current time every
minute for one day. SQL can be,
{code:java}
COUNT(*) GROUP BY USER, TUMBLE(pt, INTEVAL '1' DAY);
SET `table.exec.emit.early-fire.delay` = `60000 ms`;
{code}
And I want to use the fire time to know when was the PV exactly.
was (Author: hailong wang):
In my business, I want to compute the PV from zero to the current time every
minute for one day. SQL can be,
{code:java}
COUNT(*) GROUP BY USER, TUMBLE(pt, INTEVAL '1' DAY);
SET `table.exec.emit.early-fire.delay` = `60000 ms`;
{code}
And I want to use the fire time to know when was the PV exactly.
> Getting the emit time when `table.exec.emit.early-fire.enabled` is true
> -----------------------------------------------------------------------
>
> Key: FLINK-18686
> URL: https://issues.apache.org/jira/browse/FLINK-18686
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Affects Versions: 1.11.0
> Reporter: hailong wang
> Priority: Major
> Fix For: 1.12.0
>
>
> We can turn `table.exec.emit.early-fire.enabled` on to let window
> early-fire. But users always want to get the emit time.
> So can we support auxiliary Function to support this, may be like
> TUMBLE_EMIT, HOP_EMIT?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
