[
https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281927#comment-15281927
]
P. Taylor Goetz commented on STORM-1757:
----------------------------------------
I'm not sure I understood [~harsha_ch]'s comment either.
If the idea is to have a beam implementation front both the Core and Trident
APIs, and allow users to select which backend is used (i.e. Core or Trident),
that may be possible, but might be a little ambitious at this point (there are
things you can do in Core that you can't in Trident, and vice versa). We may
want to pick one (Core or Trident) and do a PoC to see how well it maps out.
That approach would offer a unified API (Beam) over Core/Trident, which would
be nice, but I agree with [~revans2] that it may not make sense to deprecate
the trident API since it offers some features that Beam doesn't, or at least
that don't map directly or cleanly.
> 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)
