[
https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281994#comment-15281994
]
Robert Joseph Evans commented on STORM-1757:
--------------------------------------------
I agree that having more than one official Storm API is a support/maintenance
issue, and worse it is confusing for customers. But I also see storm as a base
platform that others can build APIs/Languages on top of. If someone wants an X
compatible API on top of storm we should encourage them, and possibly add in
features to core storm to support them, but we don't necessarily pull them into
our repo. I see beam and SQL in this context.
If you don't like trident, or think we can replace it with some changes to the
normal storm API then lets think about what the correct API should be and
implement it. If beam really is the correct API and we don't think we can do
better, then storm should look at becoming the reference implementation for
open source beam, and we should deprecate both Trident and the core storm API.
But I personally don't think it is. From what I have seen the beam API is
designed very much around ETL. It does that very well. It can handle complex
windowing for you and make the job of most of my customers rather simple. This
is why I am exploring beam compatibility. But in the case of micro services
like what kafka streams appears to be targeting, or in the case IOT, is beam
the right API for that? It may grow up to be eventually, but right now it does
not appear to be at all.
> 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)
