[
https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284871#comment-15284871
]
Robert Joseph Evans commented on STORM-1757:
--------------------------------------------
I agree that going to a new API and deprecating other APIs is something that we
need to do thoughtfully and is not going to happen overnight. Perhaps it
warrants it's own JIRA for discussion/exploration.
Having multiple APIs is a pain from both a maintenance standpoint and from a
user standpoint in deciding what to do. You mean I have to rewrite things if I
don't need exactly once any more and I want better performance? It would be
nice to be able to support exactly once processing in a unified API with at
least once and at most once. Preferably something that is backwards compatible
with the existing storm core API. But I really haven't spent much time
thinking through how that API would work/look. For the most part I would
expect it could look like the check-pointing code we have now, but some
de-duping happening in there as well. Either way I think this needs to be on a
separate JIRA so we can discuss a long term plan for storm.
> 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)
