[
https://issues.apache.org/jira/browse/FLINK-24103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17452985#comment-17452985
]
Timo Walther commented on FLINK-24103:
--------------------------------------
[~monster#12] no there is still no result. It looks like a starter task but is
actually a pretty tricky topic. FLINK-24664 is a similar topic. Feel free to
suggest a solution to this.
> Create time-based LAST_VALUE / FIRST_VALUE
> ------------------------------------------
>
> Key: FLINK-24103
> URL: https://issues.apache.org/jira/browse/FLINK-24103
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Runtime
> Reporter: Timo Walther
> Priority: Major
>
> LAST_VALUE and FIRST_VALUE don't support merging. As far I can see it,
> FLINK-20110 tries to solve this by using nano second timestamps internally.
> However, an easier and consistent approach could be to allow a time parameter
> in the signature:
> {code}
> LAST_VALUE(timestamp, value)
> FIRST_VALUE(timestamp, value)
> {code}
> This allows merging based on a timestamp in HOP or SESSION windows.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
