[
https://issues.apache.org/jira/browse/STORM-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991169#comment-14991169
]
ASF GitHub Bot commented on STORM-1167:
---------------------------------------
Github user arunmahadevan commented on the pull request:
https://github.com/apache/storm/pull/855#issuecomment-153962977
@haohui Thanks for the feedback and yes your points are valid. We will
incrementally add a state store for partial results and the window state and
reduce window re-evaluation during replay. However, I am not sure if the tuples
in window should spill over to a persistent store. I think we should rely on
storm's acking mechanism to replay the events and expect that the spouts can
reliable replay the events from a persistent store (e.g. kafka). This is
consistent with storm's idea of not persisting in-transit tuples anywhere.
> Add sliding & tumbling window support for core storm
> ----------------------------------------------------
>
> Key: STORM-1167
> URL: https://issues.apache.org/jira/browse/STORM-1167
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Arun Mahadevan
> Assignee: Arun Mahadevan
>
> Currently, topologies that needs windowing support requires writing custom
> logic inside bolts making it tedious to handle the windowing and acking logic
> with custom logic.
> We can add framework level support to core storm bolts to process tuples in a
> time or a count based window. Sliding and tumbling windows can be supported.
> Later this can be extended to trident apis as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
