[
https://issues.apache.org/jira/browse/STORM-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057317#comment-15057317
]
ASF GitHub Bot commented on STORM-1187:
---------------------------------------
Github user satishd commented on a diff in the pull request:
https://github.com/apache/storm/pull/900#discussion_r47595521
--- Diff: storm-core/src/jvm/backtype/storm/windowing/EvictionPolicy.java
---
@@ -39,4 +63,12 @@
* @param event the input event to be tracked
*/
void track(Event<T> event);
+
+ /**
+ * Sets a context in the eviction policy that can be used while
evicting the events.
+ * E.g. For TimeEvictionPolicy, this could be used to set the
reference timestamp.
+ *
+ * @param context
+ */
+ void setContext(Object context);
--- End diff --
May want to introduce class/interface EvictionPolicyContext which may have
opaque structure for now. This can be done later as this PR is waiting for long.
> 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)
