[
https://issues.apache.org/jira/browse/FLINK-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771083#comment-16771083
]
Fabian Hueske commented on FLINK-11454:
---------------------------------------
The implementation logic should be similar, so we could certainly copy some
code.
I'm not sure if it is a good idea to move the logic to DataStream API (and
remove it from the SQL runtime), as there are some details like the
code-generated aggregation function that might need some workarounds.
Btw. how flexible will the slice / merge mechanism be? Do we need time-sliding
or is count-sliding enough. That should be the case if slicing is always
time-based.
> Support MergedStream operation
> ------------------------------
>
> Key: FLINK-11454
> URL: https://issues.apache.org/jira/browse/FLINK-11454
> Project: Flink
> Issue Type: Sub-task
> Components: DataStream API
> Reporter: Rong Rong
> Assignee: Rong Rong
> Priority: Major
>
> {{Following SlicedStream, the mergedStream operator merges results from
> sliced stream and produces windowing results.
> {code:java}
> val slicedStream: SlicedStream = inputStream
> .keyBy("key")
> .sliceWindow(Time.seconds(5L)) // new “slice window” concept: to
> combine
> // tumble results based on discrete
> // non-overlapping windows.
> .aggregate(aggFunc)
> val mergedStream1: MergedStream = slicedStream
> .slideOver(Time.second(10L)) // combine slice results with same
>
> // windowing function, equivalent to
> // WindowOperator with an aggregate
> state
> // and derived aggregate function.
> val mergedStream2: MergedStream = slicedStream
> .slideOver(Count.of(5))
> .apply(windowFunction) // apply a different window function
> over
> // the sliced results.{code}
> MergedStream are produced by MergeOperator:
> {{slideOver}} and {{apply}} can be combined into a {{OVER AGGREGATE}}
> implementation similar to the one in TableAPI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)