[jira] [Commented] (STORM-1873) Reemit late tuples in windowed mode

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

[GitHub] storm pull request #1355: STORM-1724 (1.x) Fill up lacking contents to Metri...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1355 --- 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

[GitHub] storm issue #1453: STORM-1873 Implement alternative behaviour for late tuple...

Github user arunmahadevan commented on the issue: https://github.com/apache/storm/pull/1453 Thanks @kosii merged to master and 1.x-branch. I did not merge to 1.0.x-branch since this adds a new api and as @ptgoetz suggested it can be targeted for 1.1.0 release. --- If your project

[jira] [Commented] (STORM-1724) Fill up lacking contents to Metrics documentation

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

[GitHub] storm pull request #1354: STORM-1724 Fill up lacking contents to Metrics doc...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1354 --- 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

[GitHub] storm pull request #1453: STORM-1873 Implement alternative behaviour for lat...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1453 --- 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

[GitHub] storm issue #1324: STORM-1700 Introduce 'whitelist' / 'blacklist' option to ...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1324 Addressed Taylor's comment: describe 'how to use' to storm.yaml.example --- 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

[jira] [Commented] (STORM-1700) Introduce 'whitelist' / 'blacklist' option to MetricsConsumer

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

[GitHub] storm issue #1324: STORM-1700 Introduce 'whitelist' / 'blacklist' option to ...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1324 @harshach OK. I'm also in doubt regarding this. Let's go with static filter and revisit if necessary. --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Commented] (STORM-1700) Introduce 'whitelist' / 'blacklist' option to MetricsConsumer

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

[GitHub] storm issue #1451: STORM-1136: Command line module to return kafka spout off...

Github user priyank5485 commented on the issue: https://github.com/apache/storm/pull/1451 @harshach Rebased 1.x branch since there were some merges since the PR was raised. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[jira] [Commented] (STORM-1136) Provide a bin script to check consumer lag from KafkaSpout to Kafka topic offsets and integrate with storm ui

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

[GitHub] storm issue #1451: STORM-1136: Command line module to return kafka spout off...

Github user priyank5485 commented on the issue: https://github.com/apache/storm/pull/1451 @abellina The tables are optional already. If there are no kafka spouts then the response will be an empty array. Can you try running a non kafka spout topology and check? I did. --- If your

[jira] [Commented] (STORM-1136) Provide a bin script to check consumer lag from KafkaSpout to Kafka topic offsets and integrate with storm ui

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

[GitHub] storm pull request #1451: STORM-1136: Command line module to return kafka sp...

Github user priyank5485 commented on a diff in the pull request: https://github.com/apache/storm/pull/1451#discussion_r66382723 --- Diff: storm-core/src/ui/public/topology.html --- @@ -384,8 +389,51 @@ Topology resources $('#topology-configuration

[jira] [Commented] (STORM-1136) Provide a bin script to check consumer lag from KafkaSpout to Kafka topic offsets and integrate with storm ui

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

[GitHub] storm pull request #1451: STORM-1136: Command line module to return kafka sp...

Github user priyank5485 commented on a diff in the pull request: https://github.com/apache/storm/pull/1451#discussion_r66382357 --- Diff: storm-core/src/ui/public/topology.html --- @@ -384,8 +389,51 @@ Topology resources $('#topology-configuration

[jira] [Commented] (STORM-1719) Introduce REST API: Topology metric stats for stream

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

[GitHub] storm pull request #1347: STORM-1719 (1.x) Introduce REST API: Topology metr...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1347 --- 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-1724) Fill up lacking contents to Metrics documentation

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

[jira] [Commented] (STORM-1719) Introduce REST API: Topology metric stats for stream

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

[GitHub] storm issue #1354: STORM-1724 Fill up lacking contents to Metrics documentat...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1354 @harshach Thanks for reviewing! I'll merge and reflect the website. --- 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

[GitHub] storm issue #1347: STORM-1719 (1.x) Introduce REST API: Topology metric stat...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1347 Sorry wrong pull request. :( --- 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

[jira] [Commented] (STORM-1719) Introduce REST API: Topology metric stats for stream

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

[GitHub] storm issue #1347: STORM-1719 (1.x) Introduce REST API: Topology metric stat...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1347 @harshach Thanks for reviewing! I'll merge and reflect the website. --- 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

[jira] [Updated] (STORM-1893) Support OpenTSDB for storing timeseries data.

[ https://issues.apache.org/jira/browse/STORM-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana updated STORM-1893: -- Description: - Implement openTSDB bolt to store timeseries data. - Trident implementation to

[jira] [Commented] (STORM-1724) Fill up lacking contents to Metrics documentation

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

[GitHub] storm issue #1354: STORM-1724 Fill up lacking contents to Metrics documentat...

Github user harshach commented on the issue: https://github.com/apache/storm/pull/1354 +1. This looks great. --- 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

[jira] [Created] (STORM-1893) Support OpenTSDB for storing timeseries data.

Satish Duggana created STORM-1893: - Summary: Support OpenTSDB for storing timeseries data. Key: STORM-1893 URL: https://issues.apache.org/jira/browse/STORM-1893 Project: Apache Storm Issue

[jira] [Commented] (STORM-1724) Fill up lacking contents to Metrics documentation

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

[GitHub] storm issue #1476: Making class TextFileReader public as it is part of the p...

Github user roshannaik commented on the issue: https://github.com/apache/storm/pull/1476 closing this PR as its a dup --- 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

[GitHub] storm pull request #1476: Making class TextFileReader public as it is part o...

Github user roshannaik closed the pull request at: https://github.com/apache/storm/pull/1476 --- 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

[GitHub] storm issue #1476: Making class TextFileReader public as it is part of the p...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1476 @roshannaik Duplicated #1461 --- 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

[GitHub] storm pull request #1476: Making class TextFileReader public as it is part o...

GitHub user roshannaik opened a pull request: https://github.com/apache/storm/pull/1476 Making class TextFileReader public as it is part of the public API for HDFS Spout minor change You can merge this pull request into a Git repository by running: $ git pull

[GitHub] storm pull request #1475: Storm 1892 - make class TextFileReader public as i...

Github user roshannaik closed the pull request at: https://github.com/apache/storm/pull/1475 --- 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

[GitHub] storm pull request #1475: Storm 1892 - make class TextFileReader public as i...

GitHub user roshannaik opened a pull request: https://github.com/apache/storm/pull/1475 Storm 1892 - make class TextFileReader public as it is part of the public API for Hdfs Spout minor fix You can merge this pull request into a Git repository by running: $ git pull

[GitHub] storm pull request #1474: support for wildcard topics ( storm-kafka-client )

Github user nabhanelrahman commented on a diff in the pull request: https://github.com/apache/storm/pull/1474#discussion_r66368337 --- Diff: external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java --- @@ -72,8 +72,10 @@ private transient

[GitHub] storm pull request #1474: support for wildcard topics ( storm-kafka-client )

Github user nabhanelrahman commented on a diff in the pull request: https://github.com/apache/storm/pull/1474#discussion_r66368331 --- Diff: external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java --- @@ -72,8 +72,10 @@ private transient

[jira] [Created] (STORM-1892) class org.apache.storm.hdfs.spout.TextFileReader should be public

Roshan Naik created STORM-1892: -- Summary: class org.apache.storm.hdfs.spout.TextFileReader should be public Key: STORM-1892 URL: https://issues.apache.org/jira/browse/STORM-1892 Project: Apache Storm

[jira] [Commented] (STORM-1865) update command line client document

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

[GitHub] storm issue #1471: STORM-1865: update command line client document

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1471 Nice work. +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

[GitHub] storm pull request #1325: STORM-1700 Introduce 'whitelist' / 'blacklist' opt...

Github user HeartSaVioR commented on a diff in the pull request: https://github.com/apache/storm/pull/1325#discussion_r66345117 --- Diff: conf/storm.yaml.example --- @@ -39,10 +39,13 @@ # - "server2" ## Metrics Consumers +## NOTE: task queue will be

[jira] [Commented] (STORM-1700) Introduce 'whitelist' / 'blacklist' option to MetricsConsumer

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

[GitHub] storm pull request #1474: support for wildcard topics ( storm-kafka-client )

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/1474#discussion_r66339764 --- Diff: external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java --- @@ -72,8 +72,10 @@ private transient boolean

[GitHub] storm pull request #1474: support for wildcard topics ( storm-kafka-client )

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/1474#discussion_r66339711 --- Diff: external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java --- @@ -72,8 +72,10 @@ private transient boolean

[GitHub] storm issue #1331: STORM-1705: Cap number of retries for a failed message

Github user ptgoetz commented on the issue: https://github.com/apache/storm/pull/1331 Two minor nits. I'm +1 once they are 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

[jira] [Commented] (STORM-1705) Cap on number of retries for a failed message in kafka spout

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

[GitHub] storm pull request #1331: STORM-1705: Cap number of retries for a failed mes...

Github user ptgoetz commented on a diff in the pull request: https://github.com/apache/storm/pull/1331#discussion_r66318933 --- Diff: external/storm-kafka/src/jvm/org/apache/storm/kafka/ExponentialBackoffMsgRetryManager.java --- @@ -86,15 +94,23 @@ public Long

[jira] [Commented] (STORM-1705) Cap on number of retries for a failed message in kafka spout

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

[GitHub] storm pull request #1331: STORM-1705: Cap number of retries for a failed mes...

Github user ptgoetz commented on a diff in the pull request: https://github.com/apache/storm/pull/1331#discussion_r66318510 --- Diff: external/storm-kafka/src/jvm/org/apache/storm/kafka/SpoutConfig.java --- @@ -37,6 +37,8 @@ public long retryInitialDelayMs = 0;

[GitHub] storm issue #1471: STORM-1865: update command line client document

Github user abhishekagarwal87 commented on the issue: https://github.com/apache/storm/pull/1471 +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

[GitHub] storm pull request #1451: STORM-1136: Command line module to return kafka sp...

Github user abellina commented on a diff in the pull request: https://github.com/apache/storm/pull/1451#discussion_r66305519 --- Diff: storm-core/src/ui/public/topology.html --- @@ -384,8 +389,51 @@ Topology resources $('#topology-configuration

[GitHub] storm issue #1451: STORM-1136: Command line module to return kafka spout off...

Github user abellina commented on the issue: https://github.com/apache/storm/pull/1451 Could the new tables be made optional? That way when a topology doesn't use KafkaSpout, the tables don't show in the UI. --- If your project is set up for it, you can reply to this email and have

[jira] [Commented] (STORM-1136) Provide a bin script to check consumer lag from KafkaSpout to Kafka topic offsets and integrate with storm ui

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

[GitHub] storm pull request #1451: STORM-1136: Command line module to return kafka sp...

Github user abellina commented on a diff in the pull request: https://github.com/apache/storm/pull/1451#discussion_r66306233 --- Diff: storm-core/src/ui/public/topology.html --- @@ -384,8 +389,51 @@ Topology resources $('#topology-configuration

[GitHub] storm pull request #1451: STORM-1136: Command line module to return kafka sp...

Github user abellina commented on a diff in the pull request: https://github.com/apache/storm/pull/1451#discussion_r66306159 --- Diff: storm-core/src/ui/public/topology.html --- @@ -384,8 +389,51 @@ Topology resources $('#topology-configuration

[jira] [Commented] (STORM-1136) Provide a bin script to check consumer lag from KafkaSpout to Kafka topic offsets and integrate with storm ui

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

[jira] [Commented] (STORM-1136) Provide a bin script to check consumer lag from KafkaSpout to Kafka topic offsets and integrate with storm ui

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

[jira] [Commented] (STORM-1742) More accurate 'complete latency'

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

[GitHub] storm issue #1379: STORM-1742 (1.x) More accurate 'complete latency'

Github user ptgoetz commented on the issue: https://github.com/apache/storm/pull/1379 I wouldn't mind seeing some larger-scale performance tests, since it doubles the size of ACK tuples (I know, they're still small). If others can confirm the absence of any performance degradation

[jira] [Commented] (STORM-1866) Update Resource Aware Scheduler Documentation

[ https://issues.apache.org/jira/browse/STORM-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320965#comment-15320965 ] P. Taylor Goetz commented on STORM-1866: [~jerrypeng] Any update on this? > Update Resource Aware

[jira] [Updated] (STORM-1873) Reemit late tuples in windowed mode

[ https://issues.apache.org/jira/browse/STORM-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1873: --- Targeted for 1.1.0 since this is an API addition. If others feel strongly that it should go into

[jira] [Commented] (STORM-1873) Reemit late tuples in windowed mode

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

[GitHub] storm issue #1453: STORM-1873 Implement alternative behaviour for late tuple...

Github user ptgoetz commented on the issue: https://github.com/apache/storm/pull/1453 +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

[jira] [Commented] (STORM-1700) Introduce 'whitelist' / 'blacklist' option to MetricsConsumer

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

[GitHub] storm issue #1324: STORM-1700 Introduce 'whitelist' / 'blacklist' option to ...

Github user ptgoetz commented on the issue: https://github.com/apache/storm/pull/1324 See my comments on #1325 as they apply here as well. --- 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

[GitHub] storm pull request #1325: STORM-1700 Introduce 'whitelist' / 'blacklist' opt...

Github user ptgoetz commented on a diff in the pull request: https://github.com/apache/storm/pull/1325#discussion_r66292563 --- Diff: conf/storm.yaml.example --- @@ -39,10 +39,13 @@ # - "server2" ## Metrics Consumers +## NOTE: task queue will be unbounded

[jira] [Commented] (STORM-1700) Introduce 'whitelist' / 'blacklist' option to MetricsConsumer

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

[jira] [Commented] (STORM-1700) Introduce 'whitelist' / 'blacklist' option to MetricsConsumer

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

[GitHub] storm pull request #1325: STORM-1700 Introduce 'whitelist' / 'blacklist' opt...

Github user ptgoetz commented on a diff in the pull request: https://github.com/apache/storm/pull/1325#discussion_r66292249 --- Diff: storm-core/src/clj/org/apache/storm/daemon/common.clj --- @@ -298,18 +299,21 @@ {[comp-id METRICS-STREAM-ID] :shuffle})

Re: Studying the evolution of Storm project

Thanks for your answer Bobby, The graphic is available at https://www.dropbox.com/s/615d0a99ynqhnnj/storm.png?dl=0 Cheers Igor Steinmacher Em qua, 8 de jun de 2016 às 12:57, Bobby Evans escreveu: > Igor, > The mailing list strips out most attachments, so if you

[jira] [Commented] (STORM-1136) Provide a bin script to check consumer lag from KafkaSpout to Kafka topic offsets and integrate with storm ui

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

[GitHub] storm issue #1451: STORM-1136: Command line module to return kafka spout off...

Github user priyank5485 commented on the issue: https://github.com/apache/storm/pull/1451 opened https://issues.apache.org/jira/browse/STORM-1891to track trident kafka spouts --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[jira] [Updated] (STORM-1891) Incorporate trident kafka spout for the kafka offset lag tool

[ https://issues.apache.org/jira/browse/STORM-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyank Shah updated STORM-1891: Description: This is a follow up JIRA to support trident kafka spouts for tool introduced in

[jira] [Created] (STORM-1891) Incorporate trident kafka spout for the kafka offset lag tool

Priyank Shah created STORM-1891: --- Summary: Incorporate trident kafka spout for the kafka offset lag tool Key: STORM-1891 URL: https://issues.apache.org/jira/browse/STORM-1891 Project: Apache Storm

[jira] [Updated] (STORM-1136) Provide a bin script to check consumer lag from KafkaSpout to Kafka topic offsets and integrate with storm ui

[ https://issues.apache.org/jira/browse/STORM-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyank Shah updated STORM-1136: Summary: Provide a bin script to check consumer lag from KafkaSpout to Kafka topic offsets and

[jira] [Commented] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320860#comment-15320860 ] Robert Joseph Evans commented on STORM-1890: Oh yes for the templates. I forgot that we were

[jira] [Commented] (STORM-1136) Provide a bin script to check consumer lag from KafkaSpout to Kafka topic offsets

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

[GitHub] storm issue #1451: STORM-1136: Command line module to return kafka spout off...

Github user harshach commented on the issue: https://github.com/apache/storm/pull/1451 Thanks @priyank5485 . This looks great and will be greatly helpful for all the users of KafkaSpout. Lets open another JIRA for trident support. +1. --- If your project is set up for it, you can

[jira] [Commented] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320848#comment-15320848 ] Alessandro Bellina commented on STORM-1890: --- There is a flag in jquery (cache:false) but it's

[jira] [Commented] (STORM-1136) Provide a bin script to check consumer lag from KafkaSpout to Kafka topic offsets

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

[jira] [Commented] (STORM-1874) Update Logger access permissions

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

[GitHub] storm issue #1456: [STORM-1874]Update logger private permissions

Github user ptgoetz commented on the issue: https://github.com/apache/storm/pull/1456 +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 feature

[jira] [Updated] (STORM-1723) Introduce ClusterMetricsConsumer

[ https://issues.apache.org/jira/browse/STORM-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1723: --- Fix Version/s: 1.1.0 2.0.0 > Introduce ClusterMetricsConsumer >

Re: Studying the evolution of Storm project

Igor, The mailing list strips out most attachments, so if you could post the image some other place that would be helpful.  One thing to realize is that storm has been on github since it was open sourced.  We migrated from https://github.com/nathanmarz/storm/ to Apache.  In Apache we first

[GitHub] storm issue #1471: STORM-1865: update command line client document

Github user ptgoetz commented on the issue: https://github.com/apache/storm/pull/1471 +1 nice job! --- 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

[jira] [Commented] (STORM-1865) update command line client document

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

[jira] [Commented] (STORM-1864) StormSubmitter should show proper error messages for submitter hook invocation.

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

[jira] [Resolved] (STORM-1864) StormSubmitter should show proper error messages for submitter hook invocation.

[ https://issues.apache.org/jira/browse/STORM-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz resolved STORM-1864. Resolution: Fixed Fix Version/s: 1.1.0 1.0.2

[GitHub] storm pull request #1473: STORM-1864 : StormSubmitter should throw respectiv...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1473 --- 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-1864) StormSubmitter should show proper error messages for submitter hook invocation.

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

[GitHub] storm issue #1473: STORM-1864 : StormSubmitter should throw respective excep...

Github user ptgoetz commented on the issue: https://github.com/apache/storm/pull/1473 +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 feature

[jira] [Resolved] (STORM-1887) Help message for the set_log_level command does not have the topology name parameter

[ https://issues.apache.org/jira/browse/STORM-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz resolved STORM-1887. Resolution: Fixed Fix Version/s: 1.1.0 2.0.0 Merged to master,

[jira] [Commented] (STORM-1887) Help message for the set_log_level command does not have the topology name parameter

[ https://issues.apache.org/jira/browse/STORM-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320740#comment-15320740 ] P. Taylor Goetz commented on STORM-1887: [~harshach] When merging to multiple branches, please

[jira] [Commented] (STORM-1889) Datatables error message displayed when viewing UI

[ https://issues.apache.org/jira/browse/STORM-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320620#comment-15320620 ] Robert Joseph Evans commented on STORM-1889: Sorry I think I put this in the wrong JIRA. >

[jira] [Commented] (STORM-1759) Viewing logs from the Storm UI doesn't work in dockerized environment

[ https://issues.apache.org/jira/browse/STORM-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320621#comment-15320621 ] Robert Joseph Evans commented on STORM-1759: I think we already have this ability.

[jira] [Commented] (STORM-1889) Datatables error message displayed when viewing UI

[ https://issues.apache.org/jira/browse/STORM-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320616#comment-15320616 ] Robert Joseph Evans commented on STORM-1889: I think we already have this ability.

[jira] [Commented] (STORM-1890) Employ cache-busting method to ensure newly deployed UI forces browsers to refetch scripts, templates, and CSS

[ https://issues.apache.org/jira/browse/STORM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320607#comment-15320607 ] Robert Joseph Evans commented on STORM-1890: That sounds great. I don't think we need that

[jira] [Commented] (STORM-1873) Reemit late tuples in windowed mode

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

[GitHub] storm issue #1453: STORM-1873 Implement alternative behaviour for late tuple...

Github user kosii commented on the issue: https://github.com/apache/storm/pull/1453 @arunmahadevan @satishd nit is fixed and commits are squashed. thanks for the review! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

  1   2   >