[
https://issues.apache.org/jira/browse/STORM-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011136#comment-15011136
]
Robert Joseph Evans commented on STORM-1187:
--------------------------------------------
Yes event time is just another dimension that we can put into buckets and
aggregate on but the hard part is knowing when you can consider a bucket
complete and when you consider a bucket completely dead and no more late data
will be accepted. A lot of this depends on your use case and where the
aggregated data is stored. I really think the cloud dataflow API captures most
of what an API like this should support. If we could make it cleaner that
would be great, but what we are doing is complex enough that I am not sure we
really can make it that much cleaner.
> Support for late and out of order events in time based windows
> --------------------------------------------------------------
>
> Key: STORM-1187
> URL: https://issues.apache.org/jira/browse/STORM-1187
> Project: Apache Storm
> Issue Type: Sub-task
> Reporter: Arun Mahadevan
> Assignee: Arun Mahadevan
>
> Right now the time based windows uses the timestamp when the tuple is
> received by the bolt.
> However there are use cases where the tuples can be processed based on the
> time when they are actually generated vs the time when they are received. So
> we need to add support for processing events with a time lag and also have
> some way to specify and read tuple timestamps.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
