torm as much as possible. JStorm is here, why not use.
>> Last point:My team is already full time on this merge, we will try our
>> best to do contribution, make Storm better.
>>
>> ThanksLongda
>>
>>
anksLongda
>
> ----------From:Sean
> Zhong Send Time:2015年11月20日(星期五) 11:58To:dev
> Subject:Re: [DISCUSS] Storm 2.0 plan
> Hi All,
>
> I think there are may be some misproper use of words or misunderstanding.
>
> Here is
> ThanksLongda
>
> ----------From:Sean
> Zhong Send Time:2015年11月20日(星期五) 11:58To:dev
> Subject:Re: [DISCUSS] Storm 2.0 plan
> Hi All,
>
> I think there are may be some misproper use of words or misunderstanding.
>
orm is here, why not use.
> Last point:My team is already full time on this merge, we will try our
> best to do contribution, make Storm better.
>
> ThanksLongda
>
> --------------From:Sean
> Zhong Send Time:2015年11月20日(星期五) 11:58T
ntribution, make Storm better.
ThanksLongda
--From:Sean
Zhong Send Time:2015年11月20日(星期五) 11:58To:dev
Subject:Re: [DISCUSS] Storm 2.0 plan
Hi All,
I think there are may be some misproper use of words or misunderstanding.
Here is what I can see both agrees these goals:
1. We want t
I am not such of fan of simply substituting the Apache Storm clojure core with
the JStorm java core either. Don't get me wrong, I would very much like to
merge the two projects together and build a stronger community but we cannot
just hastily rush this process. Like others have said the projec
Longda,
"2.1 Copy modules from JStorm, one module from one module
> 2.2 The sequence is extern
> modules/client/utils/nimbus/supervisor/drpc/worker & task/web ui/others"
Are you suggesting we just copy the Jstorm code in place of clojure? If
so thats not going to work. There might be some code t
Hi All,
I think there are may be some misproper use of words or misunderstanding.
Here is what I can see both agrees these goals:
1. We want to migrate clojure to java
2. We want to merge important features together.
3. We want to do this in a step by step, transparent, reviewable way,
especially
Very well stated Juntaek.
I should also point out that there's nothing stopping the JStorm team from
releasing new versions of JStorm, or adding new features. But you would have to
be careful to note that any such release is "JStorm" and not "Apache Storm."
And any such release cannot be hosted
Sorry Longda, but I can't help telling that I also disagree about changing
codebase.
Feature matrix shows us how far Apache Storm and JStorm are diverged, just
in point of feature's view. We can't be safe to change although feature
matrixes are identical, because feature matrix doesn't contain the
I disagree completely. You claim that JStorm is compatible with storm 1.0. I
don't believe that it is 100% compatible. There has been more then 2 years of
software development happening on both sides. Security was not done in a day,
and porting it over to JStorm is not going to happen quickl
Sorry for changing the Subject.
I am +1 for releasing Storm 2.0 with java core, which is merged with JStorm.
I think the change of this release will be the biggest one in history. It will
probably take a long time to develop. At the same time, Heron is going to open
source, and the latest relea
12 matches
Mail list logo
