[
https://issues.apache.org/jira/browse/FLINK-24001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437733#comment-17437733
]
JING ZHANG commented on FLINK-24001:
------------------------------------
After discussion with [~lzljs3620320] [~jark], it seems we have two options to
deal with row semantics window (tumble/hop/cumulate window).
# Send the data directly when receive input data instead of send data after
the end of each window
# send data after the end of each window. Require input stream shuffle by the
whole input records, it means the whole record as partition key in order to
construct a keyed stream.
[~twalthr] [~MartijnVisser] WDYT, which option is better or any other idea?
> Support evaluating individual window table-valued function in runtime
> ---------------------------------------------------------------------
>
> Key: FLINK-24001
> URL: https://issues.apache.org/jira/browse/FLINK-24001
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Runtime
> Affects Versions: 1.15.0
> Reporter: JING ZHANG
> Priority: Major
>
> {{Currently, window table-valued function has to be used with other window
> operation, such as window aggregate, window topN and window join. }}
> {{In the ticket, we aim to support evaluating individual window table-valued
> function in runtime, which means, introduce an operator to handle this.}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
