[
https://issues.apache.org/jira/browse/FLINK-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974818#comment-14974818
]
Gyula Fora commented on FLINK-2922:
-----------------------------------
I think this could be implemented nicely with the same logic I did for the
StreamKV (https://github.com/gyfora/StreamKV)
Where you create an abstract queryable object (the window). On which you apply
queries that return QueryResults from which you can get the streams. This would
abstract away the tuple logic from the user who can simple work on the streams
then.
> Add Queryable Window Operator
> -----------------------------
>
> Key: FLINK-2922
> URL: https://issues.apache.org/jira/browse/FLINK-2922
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
>
> The idea is to provide a window operator that allows to query the current
> window result at any time without discarding the current result.
> For example, a user might have an aggregation window operation with tumbling
> windows of 1 hour. Now, at any time they might be interested in the current
> aggregated value for the currently in-flight hour window.
> The idea is to make the operator a two input operator where normal elements
> arrive on input one while queries arrive on input two. The query stream must
> be keyed by the same key as the input stream. If an input arrives for a key
> the current value for that key is emitted along with the query element so
> that the user can map the result to the query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
