@storm.incubator.apache.org
Cc: d...@storm.incubator.apache.org
mailto:d...@storm.incubator.apache.orgmailto:d...@storm.incubator.apache.org
d...@storm.incubator.apache.org
mailto:d...@storm.incubator.apache.orgmailto:d...@storm.incubator.apache.org
Subject: Re: [DISCUSS] Pulling Contrib Modules into Apache
storm-kafka will be somewhat complicated by the fact that
storm-kafka-0.8-plus was forked from the original source without commit
history. We’ll also have to figure out both if to and how to maintain
compatibility with two versions of kafka. I’ll propose starting with the
original
...@storm.incubator.apache.orgmailto:d...@storm.incubator.apache.org
Subject: Re: [DISCUSS] Pulling Contrib Modules into Apache
hi, I am in agreement with Taylor and believe I understand his
intent. An incredible tool/framework/application like Storm is
only enhanced and gains value from
...@storm.incubator.apache.org
d...@storm.incubator.apache.org
mailto:d...@storm.incubator.apache.orgmailto:d...@storm.incubator.apache.org
Subject: Re: [DISCUSS] Pulling Contrib Modules into Apache
hi, I am in agreement with Taylor and believe I understand his
intent. An incredible tool/framework
@storm.incubator.apache.orgmailto:user@storm.incubator.apache.org
mailto:user@storm.incubator.apache.org
Subject: Re: [DISCUSS] Pulling Contrib Modules into Apache
Thanks for the feedback Bobby.
To clarify, I'm mainly talking about spout/bolt/trident state
implementations that integrate storm with *Technology X*, where
...@storm.incubator.apache.orgmailto:d...@storm.incubator.apache.org
d...@storm.incubator.apache.orgmailto:d...@storm.incubator.apache.org
Subject: Re: [DISCUSS] Pulling Contrib Modules into Apache
hi,
I am in agreement with Taylor and believe I understand his intent. An
incredible tool
@storm.incubator.apache.orgmailto:user@storm.incubator.apache.org
user@storm.incubator.apache.orgmailto:user@storm.incubator.apache.org
Subject: Re: [DISCUSS] Pulling Contrib Modules into Apache
Thanks for the feedback Bobby.
To clarify, I¹m mainly talking about spout/bolt/trident state
implementations
: [DISCUSS] Pulling Contrib Modules into Apache
Bobby,
FWIW, I¹d love to see storm-yarn inside. I think we could definitely make
things easier on the end-user if they were more cohesive.
e.g. Imagine if we had ³storm launch yarn² inside of $storm/bin that would
kickoff a storm-yarn launch
A while back I opened STORM-206 [1] to capture ideas for pulling in “contrib”
modules to the Apache codebase.
In the past, we had the storm-contrib github project [2] which subsequently got
broken up into individual projects hosted on the stormprocessor github group
[3] and elsewhere.
The
Just to be clear (and play a little Devil’s advocate :) ), I’m not suggesting
that whatever a “contrib” project/module/subproject might become, be a
clearinghouse for anything Storm-related.
I see it as something that is well-vetted by the Storm community, subject to
PPMC review, vote, etc.
hi,
I am in agreement with Taylor and believe I understand his intent. An
incredible tool/framework/application like Storm is only enhanced and gains
value from the number of well maintained and vetted modules that can be
used for integration and adding further functionality.
I am
11 matches
Mail list logo
