[
https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286881#comment-15286881
]
Arun Mahadevan commented on STORM-1757:
---------------------------------------
[~revans2] the current checkpointing supports at-least once and may be we could
use it as is for the initial prototype if we are ok with the guarantee. The
current implementation does not checkpoint the state of the spout, but I think
it can be extended to do so either by having the checkpoint spout co-ordinating
with user spouts via zookeeper or by having the checkpoint spout act like a
co-ordinator with user spouts running as bolts (similar to trident). I will put
more thought around this and try to come up with a prototype.
I am not sure I understand correctly the requirement for having a commit id in
rollback. The current restore happens by discarding any prepared (but
un-commited) changes or rolling forward any commits that were in progress.
> Apache Beam Runner for Storm
> ----------------------------
>
> Key: STORM-1757
> URL: https://issues.apache.org/jira/browse/STORM-1757
> Project: Apache Storm
> Issue Type: Brainstorming
> Reporter: P. Taylor Goetz
> Priority: Minor
>
> This is a call for interested parties to collaborate on an Apache Beam [1]
> runner for Storm, and express their thoughts and opinions.
> Given the addition of the Windowing API to Apache Storm, we should be able to
> map naturally to the Beam API. If not, it may be indicative of shortcomings
> of the Storm API that should be addressed.
> [1] http://beam.incubator.apache.org
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
