[ 
https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281938#comment-15281938
 ] 

Sriharsha Chintalapani commented on STORM-1757:
-----------------------------------------------

[~revans2] [~ptgoetz] 
my bad I started with "unifying APIs" :). what I meant is to have one API to do 
per tuple and micro batching instead of current situation of storm-core and 
trident. I wanted to explore if beam could be that API with which we can per 
tuple and micro batching . If its a possibility than we can slowly deprecate 
trident. 

"That approach would offer a unified API (Beam) over Core/Trident, which would 
be nice"
This what I meant in my earlier comment.

If we keep adding more APIs we only going to have more problems :). From my 
experience in talking to users, either they don't understand trident or they 
complain why they have to write in two different apis for per-tuple and micro 
batching.  If Beam is not there yet we need to re-think our current API 
approach instead of having core and trident as separate apis addressing 
different use cases we should invest in having a single API that can address 
both.

[~parth.brahmbhatt] [~satish.duggana] was suggesting using Java 8 api before in 
our discussions. I don't want to add more apis but having Single API to do both 
would be really great for users and the community.  
I don't want to derail the discussion of beam here but thought this is relevant 
to this discussion. Given we are working on java migration as part storm 2.0 I 
think we should consider having a single API for 2.0 release.



> 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)

Reply via email to