[
https://issues.apache.org/jira/browse/FLINK-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933231#comment-14933231
]
ASF GitHub Bot commented on FLINK-2677:
---------------------------------------
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/1184#issuecomment-143728731
Event-time windowing is supported if you manually enable watermarks using
`setWatermarkInterval` (it is still called `setAutoWatermarkInterval` but I
want to change this in an upcoming PR.
It is very tricky to derive a watermark interval, that's why I'm not doing
it yet. In the upcoming PR I want to add an operator that can extract
timestamps from records and also emit watermarks based on these timestamps. I
guess no one would implement a custom source for watermark emission. Most
people would use Kafka and then extract timestamps after that.
> Add a general-purpose keyed-window operator
> -------------------------------------------
>
> Key: FLINK-2677
> URL: https://issues.apache.org/jira/browse/FLINK-2677
> Project: Flink
> Issue Type: Sub-task
> Components: Streaming
> Affects Versions: 0.10
> Reporter: Stephan Ewen
> Assignee: Aljoscha Krettek
> Fix For: 0.10
>
>
> This operator should support:
> - Customizable triggers
> - Eviction on triggers: all / none / custom
> - Discard by time (expiry of state)
> - Event time time window assignment
> This set of requirements is effectively a mix between the current
> trigger/evict model and the Cloud Dataflow window definition model.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
