[jira] [Commented] (STORM-717) Proposal: JStorm contribution from Alibaba

["Longda Feng (JIRA)" <ji...@apache.org>]

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

Longda Feng commented on STORM-717:
-----------------------------------

Here is one slide to introduce JStorm http://www.slideshare.net/hustjackie/jstorm-introduction

Why we start merge ?
(1) in a long term, Java core will bring more contributors, make Storm evolve faster.
(2) the goal both Storm and JStorm are almost same, let's work together to reduce  duplication of effort.
(3) Alibaba JStorm Team are one of the most experienced teams in this field, they can bring lots of JStorm enhancement changes to Storm.
(4) There are hundreds of application in Alibaba running on JStorm, which can help to verify one RC version Storm, this will reduce release period.
(5) We can have a try to unify offline and online programming framework, merge Spark framework, some more challenege things.

The target of merge:
(1) Storm application can still be run without change user code after merge.

The problem are: 
(1) The work of merging is huge, it will take much effort of two communities, especially for some design discussion.Fortunately JStorm communities will take charge of this task.
(2) The period of Storm with both clojure core and java core maybe long, it is the biggest release since Storm release, it need more time to test.


I think all difficult of merge can be resolve, the only problem is how long we resolve them.

> Proposal: JStorm contribution from Alibaba
> ------------------------------------------
>
>                 Key: STORM-717
>                 URL: https://issues.apache.org/jira/browse/STORM-717
>             Project: Apache Storm
>          Issue Type: Umbrella
>            Reporter: Sean Zhong
>
> This is a umbrella case for the code contribution from Jstorm project. Please follow in this root jira to raise concerns and make discussions. All discussion in dev list or votes shall have a link posted in this unbrella jira.
> The suggested steps and principals:
> Principal for the JStorm contribution
> 1.      All job jars in Storm can be migrated directly without recompilation.
> 2.      Functions of JStorm will be merged into Storm.
> 3.      Most user facing function or user experience of Storm will be retained.
> 4.      There will be performance improvement.
> 5.      The process should be Smooth with incremental and tractable progress.
> Need consense and further discussion
> What is the best approach to evolve Clojure and Java(need more discussion on this) the two languages in future? More on Java?
> Proposed Steps:
> 1.      IP donation
> We should follow process of http://incubator.apache.org/ip-clearance/, 
> a)      Identity the code base,  which tag version to choose as a basis. MD5 for the code base.
> b)       IP Plan (copyright)
> c)       distribution right, ICLA
> 2.      Determine the folder layout required for Storm, so that we can then easily break the effort to module level. 
> 3.      Continue the discussion and get a consensus of everyone in community about relation of Clojure and Java.
> 4.      Define process
> a)       whether to create a Branch?
> b)       What is the target Feature list?
> c)        What is the target feature Order?
> d)       What is the target Time line?
> e)       What is the Target Version?
> References:
> Jstorm site: https://github.com/alibaba/jstorm
> Original Discussion about JStorm and Storm: http://mail-archives.apache.org/mod_mbox/storm-dev/201410.mbox/%3C005701cfef39%245efd8100%241cf88300%24%40alibaba-inc.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)