Congrats Erik.
-Harsha
On Fri, Feb 23, 2018, at 11:15 AM, Karthick Duraisamy Soundararaj wrote:
> Whoa! Congratulations, Erik. Well deserved!
>
> On Fri, Feb 23, 2018 at 10:37 AM, Erik Weathers <
> eweath...@groupon.com.invalid> wrote:
>
> > Thanks everyone! And
+1 to replace storm-kafka-client in 1.0.x branch
-Harsha
On Tue, Jan 30, 2018, at 7:04 PM, Jungtaek Lim wrote:
> Bump up this thread so that we could reach consensus earlier. Given that we
> got concern related to this, I think it is ideal to release 1.1.x/1.0.x
> with making decision and
they are addressed or any
action item is taken. We should start another thread to discuss this process as
well.
Thanks,
Harsha
On Tue, Jan 30, 2018, at 9:49 AM, Hugo Da Cruz Louro wrote:
> I think that the bahir approach makes sense for connectors that don’t
> fall into the "
.
-Harsha
On Fri, Jun 9, 2017, at 09:16 PM, Harsha wrote:
> Arun,
>For big features we did follow design doc/review. Making it
>formal makes everyone to follow a process.
> Again this process is not for bug fixes as we stated its about New
> Features/Config
+1. Deployed on a 3 node cluster and ran sample topologies.
-Harsha
On Sat, Jul 29, 2017, at 08:11 AM, Stig Rohde Døssing wrote:
> Unpacked the binary tar and built ExclamationTopology against Nexus
> staging.
> Started Nimbus, a supervisor and the UI daemon via storm.cmd.
&g
Tested source code by running unit tests and installed binaries to run
example topologies. +1.
-Harsha
On Tue, Jul 25, 2017, at 10:08 AM, Bobby Evans wrote:
> I built from source (v1.1.1 88f0b8a45553ea960164fab18c736a5cdbae8e58) ran
> all of the unit tests and ran some manual tests.
>
connector doesnt’ make sense and honestly splits the
usage which doesn’t give us any feedback on new storm-kafka-client.
Thanks,
Harsha
On Wed, Jul 19, 2017, at 09:20 AM, Hugo Da Cruz Louro wrote:
> Hi,
>
> The goal of this email is to summarize and unify the discussion started
> across s
+1 for above stated approach on releasing 1.2.0 with metrics
-Harsha
On Tue, Jun 27, 2017, at 12:17 PM, P. Taylor Goetz wrote:
> The work on metrics is ready for a pull request to 1.x-branch from the
> feature branch. I’ve held off because we haven’t reached consensus on a
> pat
er too far in the
wrong direction to bring up and improve or remove this process.
We should also as a community strive to have better quality and I am
hoping this will give us a chance to not only let users know what are
changes coming in but also keep the dev list to have a chance and join
the discussion
way to go.
-Harsha
On Jun 9, 2017, 4:09 PM -0700, Hugo Da Cruz Louro
<hlo...@hortonworks.com>, wrote:
+1 for simplifying KafkaSpoutConfig. Too many constructors and too many
methods.. I am not sure it’s justifiable to have any methods that simply
set KafkaConsumer properties. All of these proper
d for the users. The contract
here is put whatever the producer configs that users wants in the conf
object and we create producer out of that config.
Honestly these interfaces needs to be simple and let the user have
control instead of adding our interpretation.
Thanks,
Harsha
On Ju
feedback and potentially caught
any issues before the implementation.
Thanks,
Harsha
On Fri, Jun 9, 2017 at 2:24 PM Bobby Evans <ev...@yahoo-inc.com.invalid>
wrote:
Can you please explain how KIP currently works and how you would
like to see something similar in storm?
If w
to wiki to see the list of changes went into a release.
Community overall will be well informed of the changes as well. Would
like to hear your thoughts.
Thanks,
Harsha
the kafka consumer config or
properties file and forwarding it to KafkaConsumer. We made
it overly complex and unnecessary.
Thanks,
Harsha
Hi Aditya,
Thanks for your interest. We entatively planning one in June
1st week. If you haven't already please register here
https://www.meetup.com/Apache-Storm-Apache-Kafka/ . I'll keep the Storm
lists updated once we finalize the date & location.
Thanks,
Harsha
On Mon, Ap
Hi All,
We are organizing a Storm Meetup at Hortonworks HQ in Santa
Clara,CA. If you are interested in attending please RSVP here
https://www.meetup.com/Apache-Storm-Apache-Kafka/events/238975416/
Thanks,
Harsha
We should this in next release of 1.x or 2.0. I am +1 on continue with
current release.
-Harsha
On Fri, Mar 24, 2017 at 8:53 PM P. Taylor Goetz <ptgo...@gmail.com> wrote:
> The question remains if we want to do this in the 1.1.0 release, or later.
>
> If it's the 1.1.0 release
and storm-perf into top-level. We can have discussion for
storm 2.0 if we want to do
more changes.
-Harsha
On Fri, Mar 24, 2017 at 4:31 PM P. Taylor Goetz <ptgo...@gmail.com> wrote:
> If we decide to change the structure of the distribution like this, I
> think we should do it in masrw
+1 on moving non-connectors to top-level like sql and storm-perf.
Regarding storm-kafka-monitor we can move this into "util" folder or keep
in the external.
-Harsha
On Fri, Mar 24, 2017 at 2:23 AM Satish Duggana <satish.dugg...@gmail.com>
wrote:
> storm-kafka-monitor is not a
Storm 2.0 migration to java in itself is a big win and would attract wider
community and adoption. So my vote would be to resolve the first 3 items to
get a release out.
All the other featured mentioned are great to have but shouldn't be
blockers for 2.0 release.
-Harsha
On Thu, Mar 23, 2017
I propose that we continue with the release and get this patch in next
minor release (probably 1.1.1?). Users doesn't need to upgrade their
cluster to get this change
so I would say this is not a show-stopper for the release.
-Harsha
On Thu, Mar 23, 2017 at 9:18 AM P. Taylor Goetz <p
+1 for documenting and releasing.
-Harsha
On Thu, Mar 23, 2017 at 7:04 AM Jungtaek Lim <kabh...@gmail.com> wrote:
> +1 to the latter.
>
> I'm in favor of documenting the change to release note, and also docs so
> that website can be reflected. The users who are affected to the
Hi All,
We are planning on scheduling a Storm Meetup in April 1st week.
Here is the meetup link https://www.meetup.com/Apache-Storm-Apache-Kafka/.
If you are interested in talking about your use-cases in storm there is 1
more slot available, please reach out to me.
Thanks,
Harsha
-client and 1.1.0 release brings in lot of improvements
and bug-fixes.
-Harsha
On Wed, Feb 8, 2017 at 6:15 PM Jungtaek Lim <kabh...@gmail.com> wrote:
> There seems some pull requests for bugfix/improvement on
> storm-kafka-client, and some authors in PRs are not availble for now.
>
+1
Tested in 3 node vagant cluster and ran few example topologies. Looks good
and verified the signature of artifacts.
On Wed, Feb 1, 2017 at 7:13 AM Bobby Evans
wrote:
> +1 Ran some simple tests in cluster mode.
>
>
> - Bobby
>
> On Wednesday, February 1, 2017,
Trying to check the status on this release of 1.1.0. Are we going to do
this release anytime soon?
On Fri, Jan 13, 2017 at 7:50 PM S G wrote:
> Not sure if its a little late to include for the 1.1.0 and 1.0.3 releases
> now, but can we consider using zookeeper 3.4.9
discretion as they would understand
what commits are more important.
Also as reviewers one can suggest to squash the commits if additional
commits doesn't make sense.
Thanks,
Harsha
On Thu, Jan 19, 2017 at 10:29 AM Hugo Da Cruz Louro <hlo...@hortonworks.com>
wrote:
> I am strongly +1. In additi
Having integration tests run as part of the travis helps finding any
run-time issues that we might not be able to catch otherwise. Can you
please file a JIRA, Raghav who put this together might help.
Thanks,
Harsha
On Tue, Dec 27, 2016 at 6:15 AM Xin Wang <data.xinw...@gmail.com> wrote:
path there will less uses on the new version.
Critical API changes can still be possible by versioning the API.
-Harsha
On Thu, Nov 10, 2016 at 7:06 AM Kyle Nusbaum <knusb...@yahoo-inc.com.invalid>
wrote:
> On Wednesday, November 9, 2016, 7:23:09 AM CST, Harsha Chintalapani <
>
?
-Harsha
On Mon, Nov 7, 2016 at 9:16 AM Kyle Nusbaum <knusb...@yahoo-inc.com.invalid>
wrote:
I worry that making it a priority to have rolling upgrades between major
versions significantly restricts the kinds of changes that we can make,
including some kinds of changes that a major version inc
me if I am wrong here.
Thanks,
Harsha
On Mon, Nov 7, 2016 at 7:43 AM Bobby Evans <ev...@yahoo-inc.com.invalid>
wrote:
> Made a mistake and put something on private that never should have been
> there. Here is the discussion in full so far.
> In response to Jungtake removing the
ion for someone to contribute.
-Harsha
On Thu, Aug 25, 2016 at 12:14 PM P. Taylor Goetz <ptgo...@gmail.com> wrote:
> I didn’t mean to imply that the code donation would come with automatic
> committership. I would expect the SQE developers to engage with the Storm
> community and
Abhishek,
Are you looking rolling upgrade kafka cluster or storm?
Harsha
On Fri, Aug 26, 2016 at 6:18 AM Abhishek Agarwal <abhishc...@gmail.com>
wrote:
>
> On Aug 26, 2016 2:50 PM, "Abhishek Agarwal" <abhishc...@gmail.com> wrote:
>
> >
>
> >
We need to get this patch in for 0.10 release
https://github.com/apache/storm/pull/1645
Thanks,
Harsha
On Fri, Aug 26, 2016 at 7:28 AM Bobby Evans <ev...@yahoo-inc.com.invalid>
wrote:
> +1 - Bobby
>
> On Friday, August 26, 2016 9:03 AM, Jungtaek Lim <kabh...@gmail.com&g
16, 2016, at 9:18 PM, Harsha Chintalapani <st...@harsha.io>
> wrote:
> >
> > Hi All,
> >We had a discussion thread for removing Java 7 support for Storm
> > 2.0.
> > Here is a formal voting thread and the JIRA
> > https://issues.apache.org/jira/browse/STORM-2041.
> >
> > Thanks,
> > Harsha
>
>
Hi All,
We had a discussion thread for removing Java 7 support for Storm
2.0.
Here is a formal voting thread and the JIRA
https://issues.apache.org/jira/browse/STORM-2041.
Thanks,
Harsha
Do we have any user requests on releasing 0.9.x . I rather propose them to
move on to 0.10.x line and retire 0.9.x branches. There are quite few
issues that got fixed in 0.10.x release line and keep maintaining 0.9.x
line wouldn't be beneficial.
Thanks,
Harsha
On Mon, Aug 15, 2016 at 4:48 PM
://www.youtube.com/watch?v=_Q2uzRIkTd8=youtu.be
http://www.slideshare.net/HadoopSummit/managing-hadoop-hbase-and-storm-clusters-at-yahoo-scale
https://www.youtube.com/watch?v=Ib8ch-xVzbw
-Harsha
On Thu, Aug 11, 2016, at 08:42 PM, Jungtaek Lim wrote:
> Hi dev,
>
> Along with taking car
Hi All,
Dropping java 7 support on master will allow us to use the new
api in Java 8 and since the master is being used for java
migration its good to make the decision now. Let me know your
thoughts.
Thanks,
Harsha
Hi All,
Dropping java 7 support on master will allow us to use the new api in
Java 8 and since the master is being used for java migration its good to
make the decision now. Let me know your thoughts.
Thanks,
Harsha
+1 (binding)
Ran a single node cluster and tried example topologies. Verified signatures
on the artifcats.
-Harsha
On Fri, Aug 5, 2016 at 8:02 AM P. Taylor Goetz <ptgo...@apache.org> wrote:
> +1 (binding)
>
> Ran on a 3-node cluster and verified fixes.
>
> -Taylor
>
>
Congrats John & Abhishek !
-Harsha
On Tue, Jun 7, 2016, at 02:14 PM, Aaron.Dossett wrote:
> I second that!
>
> On 6/7/16, 3:12 PM, "Bobby Evans" <ev...@yahoo-inc.com.INVALID> wrote:
>
> >Congratulations to both of you. Well deserved.
> > - Bobby
&g
commented out the line that pushes to apache git repo until I get
some feedback but you can safely run it and see how the final commit
looks like.
Thanks,
Harsha
On Sun, May 15, 2016, at 07:04 PM, Jungtaek Lim wrote:
> Moving opinions from other threads,
>
> Abhishek
>
>
as
well. At least for us this is helpful to look at what went
though the patch when a user hits a similar issue.
Thanks,
Harsha
On Mon, May 16, 2016, at 01:22 PM, Erik Weathers wrote:
> :_( I was happy for a second that the comments weren't getting added to
> JIRA. I still have no
Jungtaek,
If we didn't get any conclusion. Lets continue discussion on
the same thread. You can just reply to that.
Lets not merge all discussions into major thread where we can't even
track which subject we are discussing.
Thanks,
Harsha
On Fri, May 13, 2016, at 08:56 PM
. notifications important for everyone else. if you are getting
spammed by this create a mail rule.
-Harsha
On Fri, May 13, 2016, at 07:47 AM, Aaron.Dossett wrote:
> I like the idea of squashing to a single commit and tagging that commit
> and PR with the JIRA ID. Agree that limiting duplicate emails
Bobby,
Can you check if I am part of commiters list. I don't see admin
page for STORM project jira.
Thanks,
Harsha
On Thu, May 12, 2016, at 02:23 PM, Hugo Da Cruz Louro wrote:
> Thanks Bobby. It’s working now.
>
> > On May 12, 2016, at 1:48 PM, Bobby Evans
Roshan,
This is 0.10 maint release . We are not going to include the
new features that went into 1.0.
+1 (binding)
Deployed on a 3-node cluster
Ran example topologies
verified signatures of binaries.
Thanks,
Harsha
On Tue, May 3, 2016, at 05:16 PM, Roshan Naik wrote
+1 (binding)
- Deployed 3-node cluster and example topologies
- Verified the binaries signature.
Thanks,
Harsha
On Sun, May 1, 2016, at 07:11 PM, Jungtaek Lim wrote:
> +1 (binding)
>
> - build succeed from source code
> - binary extracted well, and supervisor launches work
storm-env.sh introduced if users want override any environment
variables. we can either comment out the line as default or what Taylor
proposed looks good too.
-Harsha
On Thu, Apr 28, 2016, at 08:27 AM, P. Taylor Goetz wrote:
> HDP uses storm-env.sh, which is where it came from. That makes se
Same as 1.0.1 release. I would like to get those two patches in for
0.10.1 release as well.
Thanks,
Harsha
On Tue, Apr 26, 2016, at 05:27 PM, Jungtaek Lim wrote:
> Same on 1.0.1 RC1, but only STORM-1731
> <https://issues.apache.org/jira/browse/STORM-1731> is affected to 0.10.1
I am +1 on doing another release candidate with these fixes in. Nice
work Jungtaek.
Thanks,
Harsha
On Tue, Apr 26, 2016, at 05:23 PM, Jungtaek Lim wrote:
> I've observed the points of performance hit (STORM-1729
> <https://issues.apache.org/jira/browse/STORM-1729>, STORM-1
we would have all cluster details including topologies as
well.
Thanks,
Harsha
On Mon, Apr 18, 2016, at 10:18 PM, Jungtaek Lim wrote:
> Cody,
>
> Great idea! Let's try it out.
> I'll send the mail to user@ regarding use cases or concerns of metrics on
> Apach
the
storm.zookeeper.root node and not touch any other nodes in
the zookeeper.
-Harsha
On Fri, Apr 15, 2016, at 11:17 AM, Hugo Da Cruz Louro wrote:
> Agree with Jungtaek.
>
> With the new KafkaSpout we should not have to worry about preserving
> offsets, as it’s done by Kafk
Erik,
Thanks. Missed that. I think we should default to that
especially to support the rolling upgrade part.
Thanks,
Harsha
On Thu, Apr 14, 2016, at 10:47 AM, Erik Weathers wrote:
> hey Harsha,
>
> Did you see Abhishek's emailt to the list yesterday?
>
> In the
.
Why not we package backtype.storm and add @deprecated to this
package and keep it in lib folder for couple of releases and
have a plan around removing it in future versions.
Thanks,
Harsha
+1 (binding)
Tested in a 3 node cluster with example topologies.
Checked the binaries.
Thanks,
Harsha
On Thu, Apr 7, 2016, at 10:02 PM, John Fang wrote:
> +1
>
> Regards
>John Fang
>
>
>
> -邮件原件-
> 发件人: Bobby Evans [mailto:ev...@yahoo-inc.com.IN
Taylor,
Lets do another release build since we have other jiras merged
in .
Thanks,
Harsha
On Mon, Apr 4, 2016, at 02:07 PM, P. Taylor Goetz wrote:
> FYI I’ve merged fixes for following to the 1.x-branch:
> * STORM-1670: LocalState#get(String) can throw FileNotFoundExc
For rc2 please include STORM-1670 as well. Source distribution is
important as well.
-Harsha
On Sat, Apr 2, 2016, at 01:02 AM, Jungtaek Lim wrote:
> Here's my test,
>
> - testing with source distribution : FAIL
> - unzip : OK
> - building from source dist : FAIL
>
on is that we should not reinvent the wheel (aka
> > > > distributed fault tolerant metrics) ourselves. The local file
> > > > blobstore with nimbus HA was a big enough pain to write and it is
> > > > relatively simple in comparison.
> > > > If the JStorm c
.
--Harsha
On Mon, Mar 21, 2016, at 08:49 AM, Abhishek Agarwal wrote:
> @Cody - The design looks good. Does the design allow to aggregate metrics
> at the task/executor level? Basically, number of distinct metrics is
> proportional to the number of distinct tasks, did you
Hi Sourav,
I just took a look. This looks great. It would be great if
you can contribute to this connector Apache Storm. If so
can you please open a JIRA and open a PR
https://github.com/apache/storm.
Thanks,
Harsha
On Sun, Mar 20, 2016, at 08
version of storm but relevant for the latest as well.
-Harsha
On Sun, Mar 13, 2016, at 01:43 PM, vibha goyal wrote:
> Hi,
>
> I am grad student, and I am working on Storm as a part of my course
> project.
>
> I have cloned the source code from git, and followed the instruction
offlate. Underneath it uses
jersey and one can run jetty server as well which is what we've as the
UI and logviewer server.
-Harsha
On Tue, Feb 23, 2016, at 08:23 AM, Ravi Sharma wrote:
> spring boot +
>
> Ravi
>
> On Tue, Feb 23, 2016 at 3:16 PM, Ankur Garg <ankurga..
ed more than single machine or not ?
>
> how it can be in distributed mode in single machine ?
>
>
> Thanks for your help
>
>
>
> On Thu, Dec 24, 2015 at 7:43 PM, Harsha <st...@harsha.io> wrote:
>
> > In storm, local mode means you run by using LocalCluster
host.name
-Harsha
On Thu, Dec 24, 2015, at 11:12 AM, researcher cs wrote:
> thanks i checked the link it's good for me but the question that i'm
> searching about
> 1- is production mode means distributed mode ?
> 2- if question 1 = yes , is that mean working on more than one machine ?
&g
not quite sure about what you mean by importing a topology that run
in two modes in local or production. In the first link I gave you ,
wordcount topology can run local cluster and on distributed as well.
-Harsha
On Thu, Dec 24, 2015, at 08:54 AM, researcher cs wrote:
> can i find help ?
>
> On
Sam,
you might be using very old version of storm since its showing
ZeroMQ. Can you try using newer version storm without zero mq.
-Harsha
On Wed, Dec 9, 2015, at 10:19 AM, sam mohel wrote:
> I have this problem since 4months when I submitted topology I
Congrats everyone.
-Harsha
On Tue, Dec 8, 2015, at 03:19 PM, Priyank Shah wrote:
> Congratulation everyone!
>
>
>
>
> On 12/8/15, 3:17 PM, "Hugo Da Cruz Louro" <hlo...@hortonworks.com> wrote:
>
> >Congrats everyone. Looking forward to working wi
Hi John, Thanks for the doc about supervisor. Could you please
add this to wiki here
https://cwiki.apache.org/confluence/display/STORM/Storm+Home and start
a discussion thread around it.
Thanks, Harsha On Fri, Nov 27, 2015, at 04:15 AM, John Fang wrote:
>
> Email had 1 atta
.
Thanks,
Harsha
On Fri, Nov 20, 2015, at 01:03 AM, Longda Feng wrote:
>
> @Sean, Thanks for clarify.
> @Taylor, @Bobby, @Sean, @Jungtaek, @Harsha, @dev,
> Sorry for leading to misunderstanding.
> The biggest point:We would like to merge two community into one
> community, One com
Taylor,
Can you add me to the wiki as well my id is "harsha".
Thanks,
Harsha
On Fri, Nov 20, 2015, at 01:19 AM, Longda Feng wrote:
> @Taylor, I want to work with Bobby, my wiki name is "longda".
> ThanksLongda--
from JStorm we should do
that .
Thanks,
Harsha
On Wed, Nov 18, 2015, at 10:13 PM, Longda Feng wrote:
> 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 bigge
+1 on Bobby's suggestion on moving the packages to storm-compat and have
it part of lib folder.
Moving 1.0 with org.apache.storm will make it easier in the future
rather than wait for 2.0 release we should make
this change now and in 2.0 we can remove the storm-compat jar.
Thanks,
Harsha
n among storm community along with
jstorm. We need to come up with plan of action on what code needs to be
merged into storm-core. I am thinking it will help better to have
everyone over video chat or something to go over the code and get it
migrated to java.
Thanks, Harsha
On Tue, Nov 10, 2015,
Bit more details on windows. We do have builds going internally on
windows , but not the latest trunk which we will be doing soon.
Regarding auth-test yes thats an issue and storm security in general not
going to work in windows. We disable this test for windows. I think we
should put a check in
enarios for testing, with/without
> > security. Talking to Kafka, Hadoop(HBase, HDFS, Hive), redis,
> > elastasearch, etc.
> > These would be run frequently but not necessarily a part of CI initially.
> > - Bobby
> >
> >
> >On Wednesday, November 4, 2015
Thanks Longda. Can you update this JIRA with list of tests cases that
you are running in this JIRA
https://issues.apache.org/jira/browse/STORM-1179
-Harsha
On Thu, Nov 5, 2015, at 08:32 PM, 封仲淹(纪君祥LongdaFeng) wrote:
> +1
> By the way, Tong(王桐) can work for this. Tong is respo
Welcome JStorm community. Thanks for your contributions to JStorm and
looking forward to working with you to make Storm better.
Thanks, Harsha
On Tue, Nov 3, 2015, at 02:05 PM, P. Taylor Goetz wrote:
> For those who may not be aware, Alibaba has donated JStorm to Apache
> Storm, and w
+1
1. Ran the unit tests
2. Verified artifacts
3. Ran a cluster deployed example topologies.
-Harsha
On Thu, Oct 29, 2015, at 09:45 AM, P. Taylor Goetz wrote:
> Yes, I’ve seen that. It has something to do with clojure tests and the
> maven lifecycle.
>
> I typically just do `mvn c
+1 (binding)
-Harsha
On Tue, Oct 27, 2015, at 12:10 PM, Priyank Shah wrote:
> +1
>
> From: "P. Taylor Goetz"
> Reply-To: <dev@storm.apache.org<mailto:dev@storm.apache.org>>
> Date: Tuesday, October 27, 2015 at 11:05 AM
> To: <dev@storm.apache.org&
+1
1. Ran unit tests
2. Deployed example topologies
3. Verified artifacts
-Harsha
On Mon, Oct 26, 2015, at 07:23 AM, Bobby Evans wrote:
> +1 looks good, built from the git tag and ran some simple test.
> - Bobby
>
>
> On Friday, October 23, 2015 9:47 PM, 임정택 <kabh..
://github.com/apache/storm/blob/master/SECURITY.md
-Harsha
On Mon, Sep 14, 2015, at 03:10 PM, Erik Weathers wrote:
> It seems that in storm 0.10 we have native code (C) that is being used
> for
> launching workers. I haven't found any reference to how this might
> affect
> deploymen
Taylor,
STORM-1039 & STORM-1042 are blockers without these UI won't
work. We need to include these in the release as well.
Thanks,
Harsha
On Fri, Sep 11, 2015, at 10:41 PM, 임정택 wrote:
> +1
>
> - test passed : OK
> -- extract source tar
> -- build via
Hi Juniman,
Thanks for the mail. Can you send us your logo I'll get it
included in the new storm website.
Thanks,
Harsha
On Wed, Sep 9, 2015, at 09:47 PM, Juniman Kasman wrote:
> Hi storm team,
> We are using Storm and would like to be added below
with all of its
dependencies included in the jar.
Thanks,
Harsha
On July 29, 2015 at 11:57:19 PM, Abhishek Agarwal (abhishc...@gmail.com) wrote:
Currently, as far as I know one has to package all the dependencies into
one jar and then submit it along with topology class. StormSubmitter
interface
:). As others noted we are
very much active and motivated community to make storm even better.
Thanks,
Harsha
On Sat, Jul 18, 2015, at 11:39 AM, Parth Brahmbhatt wrote:
Have you seen this
http://yahoohadoop.tumblr.com/post/122544585051/apache-storm-roadmap-at-yah
oo ? Or if you still have
If you are interested in attending bay area meetup for Apache Storm Kafka .
Please join the group here
http://www.meetup.com/Apache-Storm-Apache-Kafka/
Thanks,
Harsha
Tim,
If its production cluster I highly recommend having zk cluster
with at least 3 nodes. So that your cluster survives in case of
zk nodes going down.
Thanks,
Harsha
On Thu, Jun 18, 2015, at 06:07 AM, Paul Poulosky wrote:
The machine that you submit your topology
+1 for the release.
1) verified keys on all release artifacts.
2) verified deploying topologies in secure and non-secure cluster.
--
Harsha
On June 8, 2015 at 12:06:31 PM, Parth Brahmbhatt (pbrahmbh...@hortonworks.com)
wrote:
+1. Agree about not blocking the release.
‹ unit tests passed
+1 (binding)
Verified installing a cluster and running example topologies.
Verified release artifacts keys asc, sha and md5.
Thanks,
Harsha
On May 29, 2015 at 4:43:38 PM, 임정택 (kabh...@gmail.com) wrote:
- test passed : OK
- extract source tar : OK
- build via mvn clean install” : OK
down all the commits that went in for a particular JIRA.
I am proposing we should squash these multiple commits into one singe commit
before merging into trunk and associate the STORM JIRA in commit message.
Let me know what you think.
Thanks,
Harsha
Hi,
For storm 0.10.0 please add if you want any JIRAs that should be
included.
I want to include https://issues.apache.org/jira/browse/STORM-617
Thanks,
Harsha
On March 12, 2015 at 9:30:25 AM, T B (thomas...@arcor.de) wrote:
Hi,
For storm 0.10.0 please add if you want any JIRAs
Taylor,
STORM-617 is on me I’ll send a patch in next couple of days.
Thanks,
Harsha
On March 19, 2015 at 1:05:21 PM, P. Taylor Goetz (ptgo...@gmail.com) wrote:
With the VOTE underway for a 0.9.4 release ( if you have time, please evaluate
the RC and vote accordingly), I’d like
Hi Oleg,
Here is a JIRA https://issues.apache.org/jira/browse/STORM-710 to start
on.
Thanks,
Harsha
On March 18, 2015 at 9:34:36 AM, Oleg Ostashchuk (ostas...@fel.cvut.cz) wrote:
Hello,
I would like to contribute to Apache Storm project. Can you please
advise me some issue or work
Sorry for the late reply. I am +1 on releasing 0.9.4 . For 0.10.0 I would like
to include this https://issues.apache.org/jira/browse/STORM-617
Thanks,
Harsha
On March 11, 2015 at 1:52:02 PM, P. Taylor Goetz (ptgo...@gmail.com) wrote:
Sorry for the late reply. I am +1 on releasing 0.9.4
Congrats Thomas and Welcome :)
--
Harsha
On March 10, 2015 at 11:09:05 AM, P. Taylor Goetz (ptgo...@apache.org) wrote:
Please join me in welcoming Thomas Becker (wurstmeister) as a new Apache Storm
Committer/PMC member.
Thomas has made significant contributions to the Storm codebase
+1
-Harsha
On Thu, Feb 19, 2015, at 07:48 AM, Melan Nimesh wrote:
+1
On Thu, Feb 19, 2015 at 9:08 PM, Nathan Marz nat...@nathanmarz.com
wrote:
+1
On Thu, Feb 19, 2015 at 8:15 AM, Andy Feng andy.f...@gmail.com wrote:
+1
Andy Feng
Sent from my iPhone
On Feb 18
)
.withFileNameFormat(fileNameformat)
.withRecordFormat(format)
.withRotationPolicy(rotationPolicy)
.withSynPolicy(syncPolicy);
The above is all that needed to use namenode HA with your storm-hdfs.
-Harsha
On Thu, Feb 19, 2015, at 08:58 AM, Bobby Evans wrote
-inc.com.invalid
wrote:
I am fine with this. I mostly want a starting point, and we can
adjust
things from there is need be.
- Bobby
On Sunday, February 8, 2015 8:39 PM, Harsha st...@harsha.io
wrote:
Thanks for putting this together. Proposed bylaws looks good
1 - 100 of 122 matches
Mail list logo