Too many machine mails

There seems to be a surplus of automatically-generated emails on the dev mailing list. Github and Apache's Jira constantly send mails to the dev list. I'm not sure that anyone finds these useful. Even if they do, I wonder if its better to move them to a separate list. It's possible that

[jira] [Commented] (STORM-2032) "not fast enough" metrics WARN message in netty client can be misinterpreted

[ https://issues.apache.org/jira/browse/STORM-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416534#comment-15416534 ] ASF GitHub Bot commented on STORM-2032: --- Github user HeartSaVioR commented on a diff in the pull

[GitHub] storm pull request #1618: [STORM-2032] removes warning in case more than one...

Github user HeartSaVioR commented on a diff in the pull request: https://github.com/apache/storm/pull/1618#discussion_r74367640 --- Diff: storm-core/src/jvm/org/apache/storm/messaging/netty/StormClientHandler.java --- @@ -60,7 +60,6 @@ public void

[GitHub] storm issue #1592: STORM-1994: Add table with per-topology and worker resour...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1592 @jerrypeng Please let me know the issue numbers for these things. I'd also try to get some time to backport them. @knusbaum Agreed. I recently initiated discussion to reduce the scope for

[jira] [Commented] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416527#comment-15416527 ] ASF GitHub Bot commented on STORM-1994: --- Github user HeartSaVioR commented on the issue:

[jira] [Commented] (STORM-2016) Topology submission improvement: support adding local jars and maven artifacts on submission

[ https://issues.apache.org/jira/browse/STORM-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416523#comment-15416523 ] ASF GitHub Bot commented on STORM-2016: --- Github user HeartSaVioR commented on a diff in the pull

[GitHub] storm pull request #1608: STORM-2016 Topology submission improvement: suppor...

Github user HeartSaVioR commented on a diff in the pull request: https://github.com/apache/storm/pull/1608#discussion_r74367408 --- Diff: bin/storm.py --- @@ -232,44 +271,91 @@ def jar(jarfile, klass, *args): The process is configured so that StormSubmitter

[GitHub] storm pull request #1608: STORM-2016 Topology submission improvement: suppor...

Github user HeartSaVioR commented on a diff in the pull request: https://github.com/apache/storm/pull/1608#discussion_r74367004 --- Diff: bin/storm.py --- @@ -754,18 +827,24 @@ def parse_config_opts(args): elif token == "--config": global CONFFILE

[jira] [Commented] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416508#comment-15416508 ] ASF GitHub Bot commented on STORM-1994: --- Github user knusbaum commented on the issue:

[GitHub] storm issue #1592: STORM-1994: Add table with per-topology and worker resour...

Github user knusbaum commented on the issue: https://github.com/apache/storm/pull/1592 @HeartSaVioR Good to hear it. I don't know if we want to stop feature development on 1.x since that's our release branch, and 2.x seems to have stalled. The policy behind all of this is

[jira] [Commented] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416500#comment-15416500 ] ASF GitHub Bot commented on STORM-1994: --- Github user HeartSaVioR commented on the issue:

[GitHub] storm issue #1592: STORM-1994: Add table with per-topology and worker resour...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1592 @knusbaum @jerrypeng OK. I was just not sure that we are seeing same target version for the improvements: 1.x vs 2.x. If we all think we would want to ship our effort to 1.x, we must not

[GitHub] storm issue #1610: STORM-2023 Add calcite-core to dependency of storm-sql-ru...

Github user harshach commented on the issue: https://github.com/apache/storm/pull/1610 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] storm issue #1592: STORM-1994: Add table with per-topology and worker resour...

Github user jerrypeng commented on the issue: https://github.com/apache/storm/pull/1592 @HeartSaVioR I have pushed critical bug fixes for RAS to the 1.x branch. There has been a few algorithmic improvements on RAS that I had only put into 2.x but I desire to get them into

[jira] [Commented] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416493#comment-15416493 ] ASF GitHub Bot commented on STORM-1994: --- Github user jerrypeng commented on the issue:

[GitHub] storm issue #1592: STORM-1994: Add table with per-topology and worker resour...

Github user abellina commented on the issue: https://github.com/apache/storm/pull/1592 @HeartSaVioR, the patch isn't directed for RAS specifically. The primary benefit for either non-RAS or RAS is summarizing all workers for a topology in one table, and all workers for a

[jira] [Commented] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416490#comment-15416490 ] ASF GitHub Bot commented on STORM-1994: --- Github user abellina commented on the issue:

[jira] [Commented] (STORM-2016) Topology submission improvement: support adding local jars and maven artifacts on submission

[ https://issues.apache.org/jira/browse/STORM-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416489#comment-15416489 ] ASF GitHub Bot commented on STORM-2016: --- Github user harshach commented on a diff in the pull

[GitHub] storm pull request #1608: STORM-2016 Topology submission improvement: suppor...

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/1608#discussion_r74366031 --- Diff: bin/storm.py --- @@ -754,18 +827,24 @@ def parse_config_opts(args): elif token == "--config": global CONFFILE

[jira] [Commented] (STORM-2016) Topology submission improvement: support adding local jars and maven artifacts on submission

[ https://issues.apache.org/jira/browse/STORM-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416487#comment-15416487 ] ASF GitHub Bot commented on STORM-2016: --- Github user harshach commented on a diff in the pull

[GitHub] storm pull request #1608: STORM-2016 Topology submission improvement: suppor...

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/1608#discussion_r74365965 --- Diff: bin/storm.py --- @@ -232,44 +271,91 @@ def jar(jarfile, klass, *args): The process is configured so that StormSubmitter

[jira] [Commented] (STORM-2032) "not fast enough" metrics WARN message in netty client can be misinterpreted

[ https://issues.apache.org/jira/browse/STORM-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416471#comment-15416471 ] ASF GitHub Bot commented on STORM-2032: --- Github user satishd commented on the issue:

[GitHub] storm issue #1618: [STORM-2032] removes warning in case more than one metric...

Github user satishd commented on the issue: https://github.com/apache/storm/pull/1618 +1, would like minor nit to be addressed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[jira] [Commented] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416470#comment-15416470 ] ASF GitHub Bot commented on STORM-1994: --- Github user knusbaum commented on the issue:

[GitHub] storm issue #1592: STORM-1994: Add table with per-topology and worker resour...

Github user knusbaum commented on the issue: https://github.com/apache/storm/pull/1592 @HeartSaVioR I'm +1 for the patch. Nimbus has been in progress for porting for a long time. We can't (apparently) halt all progress until it's ported. You recently submitted a patch

[GitHub] storm pull request #1618: [STORM-2032] removes warning in case more than one...

Github user satishd commented on a diff in the pull request: https://github.com/apache/storm/pull/1618#discussion_r74365279 --- Diff: storm-core/src/jvm/org/apache/storm/messaging/netty/StormClientHandler.java --- @@ -60,7 +60,6 @@ public void messageReceived(ChannelHandlerContext

[jira] [Commented] (STORM-2032) "not fast enough" metrics WARN message in netty client can be misinterpreted

[ https://issues.apache.org/jira/browse/STORM-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416468#comment-15416468 ] ASF GitHub Bot commented on STORM-2032: --- Github user satishd commented on a diff in the pull

[jira] [Commented] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416465#comment-15416465 ] ASF GitHub Bot commented on STORM-1994: --- Github user HeartSaVioR commented on the issue:

[GitHub] storm issue #1592: STORM-1994: Add table with per-topology and worker resour...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1592 @abellina First of all, freezing development was what we planned though it was broken now. Let me clear on this, - Recent patches for RAS are only applied to master (2.0.0)

[GitHub] storm issue #1592: STORM-1994: Add table with per-topology and worker resour...

Github user abellina commented on the issue: https://github.com/apache/storm/pull/1592 @HeartSaVioR, Are we freezing development on nimbus until it is ported? I can wait and submit when that is ported if nimbus is close, else I am not sure if it is a show stopper. Maybe I

[jira] [Commented] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416448#comment-15416448 ] ASF GitHub Bot commented on STORM-1994: --- Github user abellina commented on the issue:

[jira] [Commented] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416389#comment-15416389 ] ASF GitHub Bot commented on STORM-1994: --- Github user HeartSaVioR commented on the issue:

[GitHub] storm issue #1592: STORM-1994: Add table with per-topology and worker resour...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1592 Hi @abellina, this is a bit huge patch (even without thrift generated code) including front-end change, so seems not easy for me to have time to review. Before reviewing, two

[jira] [Commented] (STORM-2032) "not fast enough" metrics WARN message in netty client can be misinterpreted

[ https://issues.apache.org/jira/browse/STORM-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416361#comment-15416361 ] ASF GitHub Bot commented on STORM-2032: --- Github user HeartSaVioR commented on a diff in the pull

[GitHub] storm pull request #1618: [STORM-2032] removes warning in case more than one...

Github user HeartSaVioR commented on a diff in the pull request: https://github.com/apache/storm/pull/1618#discussion_r74361223 --- Diff: storm-core/src/jvm/org/apache/storm/messaging/netty/StormClientHandler.java --- @@ -60,7 +60,6 @@ public void

Re: New Storm Commiter/PMC Member: Satish Duggana

Congratulations!! 2016-08-11 6:59 GMT+08:00 Hugo Da Cruz Louro : > Congratulations Satish. > > > On Aug 10, 2016, at 6:31 AM, Bobby Evans > wrote: > > > > Congratulations > > - Bobby > > > >On Tuesday, August 9, 2016 5:05 PM,

Re: New Storm Commiter/PMC Member: Satish Duggana

Congratulations Satish. > On Aug 10, 2016, at 6:31 AM, Bobby Evans wrote: > > Congratulations > - Bobby > >On Tuesday, August 9, 2016 5:05 PM, Jungtaek Lim wrote: > > > Congrats Satish! > > Jungtaek Lim (HeartSaVioR) > > On

[ANNOUNCE] Apache Storm 1.0.2 Released

The Apache Storm community is pleased to announce the release of Apache Storm version 1.0.2. Storm is a distributed, fault-tolerant, and high-performance realtime computation system that provides strong guarantees on the processing of data. You can read more about Storm on the project website:

[jira] [Commented] (STORM-1994) Add table with per-topology & worker resource usage and components in (new) supervisor and topology pages

[ https://issues.apache.org/jira/browse/STORM-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415515#comment-15415515 ] ASF GitHub Bot commented on STORM-1994: --- Github user abellina commented on the issue:

[GitHub] storm issue #1592: STORM-1994: Add table with per-topology and worker resour...

Github user abellina commented on the issue: https://github.com/apache/storm/pull/1592 Hi, I haven't gotten reviews on this ticket yet. There are a lot of generated files, so it is not as bad as it looks! --- If your project is set up for it, you can reply to this email and have

[GitHub] storm pull request #1618: [STORM-2032] removes warning in case more than one...

GitHub user d2r opened a pull request: https://github.com/apache/storm/pull/1618 [STORM-2032] removes warning in case more than one metrics tuple is received You can merge this pull request into a Git repository by running: $ git pull https://github.com/d2r/storm

[jira] [Commented] (STORM-2032) "not fast enough" metrics WARN message in netty client can be misinterpreted

[ https://issues.apache.org/jira/browse/STORM-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415443#comment-15415443 ] ASF GitHub Bot commented on STORM-2032: --- GitHub user d2r opened a pull request:

[jira] [Created] (STORM-2032) "not fast enough" metrics WARN message in netty client can be misinterpreted

Derek Dagit created STORM-2032: -- Summary: "not fast enough" metrics WARN message in netty client can be misinterpreted Key: STORM-2032 URL: https://issues.apache.org/jira/browse/STORM-2032 Project:

[jira] [Created] (STORM-2031) Multilang: support distribute cache API a.k.a BlobStore

Jungtaek Lim created STORM-2031: --- Summary: Multilang: support distribute cache API a.k.a BlobStore Key: STORM-2031 URL: https://issues.apache.org/jira/browse/STORM-2031 Project: Apache Storm

[jira] [Created] (STORM-2030) Multilang: support stateful bolt

Jungtaek Lim created STORM-2030: --- Summary: Multilang: support stateful bolt Key: STORM-2030 URL: https://issues.apache.org/jira/browse/STORM-2030 Project: Apache Storm Issue Type: Improvement

[jira] [Created] (STORM-2029) Multilang: support windowing feature

Jungtaek Lim created STORM-2029: --- Summary: Multilang: support windowing feature Key: STORM-2029 URL: https://issues.apache.org/jira/browse/STORM-2029 Project: Apache Storm Issue Type:

[jira] [Commented] (STORM-2026) Inconsistency between (SpoutExecutor, BoltExecutor) and (spout-transfer-fn, bolt-transfer-fn)

[ https://issues.apache.org/jira/browse/STORM-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415284#comment-15415284 ] ASF GitHub Bot commented on STORM-2026: --- Github user HeartSaVioR commented on the issue:

[GitHub] storm issue #1616: STORM-2026 Inconsistency between (SpoutExecutor, BoltExec...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1616 Thanks @satishd for reviewing and merging! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

Re: New Storm Commiter/PMC Member: Satish Duggana

Congratulations  - Bobby On Tuesday, August 9, 2016 5:05 PM, Jungtaek Lim wrote: Congrats Satish! Jungtaek Lim (HeartSaVioR) On Wednesday, August 10, 2016, Matthias J. Sax wrote: > Congrats Satish! > > -Matthias > > On 08/09/2016 10:21 PM, P.

[jira] [Commented] (STORM-2016) Topology submission improvement: support adding local jars and maven artifacts on submission

[ https://issues.apache.org/jira/browse/STORM-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415221#comment-15415221 ] ASF GitHub Bot commented on STORM-2016: --- Github user manuzhang commented on the issue:

[jira] [Updated] (STORM-2026) Inconsistency between (SpoutExecutor, BoltExecutor) and (spout-transfer-fn, bolt-transfer-fn)

[ https://issues.apache.org/jira/browse/STORM-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2026: Fix Version/s: 2.0.0 > Inconsistency between (SpoutExecutor, BoltExecutor) and (spout-transfer-fn,

[GitHub] storm issue #1608: STORM-2016 Topology submission improvement: support addin...

Github user manuzhang commented on the issue: https://github.com/apache/storm/pull/1608 The exception is caused by the escaping "\" character previously. Things are working now after I updated to the latest version. --- If your project is set up for it, you can reply to this email

[jira] [Commented] (STORM-2026) Inconsistency between (SpoutExecutor, BoltExecutor) and (spout-transfer-fn, bolt-transfer-fn)

[ https://issues.apache.org/jira/browse/STORM-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415149#comment-15415149 ] ASF GitHub Bot commented on STORM-2026: --- Github user satishd commented on the issue:

[GitHub] storm issue #1616: STORM-2026 Inconsistency between (SpoutExecutor, BoltExec...

Github user satishd commented on the issue: https://github.com/apache/storm/pull/1616 Thanks @HeartSaVioR --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so,

[jira] [Commented] (STORM-2026) Inconsistency between (SpoutExecutor, BoltExecutor) and (spout-transfer-fn, bolt-transfer-fn)

[ https://issues.apache.org/jira/browse/STORM-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415148#comment-15415148 ] ASF GitHub Bot commented on STORM-2026: --- Github user asfgit closed the pull request at:

[GitHub] storm pull request #1616: STORM-2026 Inconsistency between (SpoutExecutor, B...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1616 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (STORM-2016) Topology submission improvement: support adding local jars and maven artifacts on submission

[ https://issues.apache.org/jira/browse/STORM-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414985#comment-15414985 ] ASF GitHub Bot commented on STORM-2016: --- Github user HeartSaVioR commented on the issue:

[GitHub] storm issue #1608: STORM-2016 Topology submission improvement: support addin...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1608 @manuzhang A bit confusing so would like to double check on this. Do you succeed to resolve 1.1.1-SNAPSHOT after `mvn clean install`? Or you're still failing? --- If your project is set up for