[jira] [Commented] (STORM-1956) Disable Backpressure by default

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

[GitHub] storm issue #1548: STORM-1956 - Disabling Backpressure by default

Github user harshach commented on the issue: https://github.com/apache/storm/pull/1548 +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 pull request #1548: STORM-1956 - Disabling Backpressure by default

GitHub user roshannaik opened a pull request: https://github.com/apache/storm/pull/1548 STORM-1956 - Disabling Backpressure by default You can merge this pull request into a Git repository by running: $ git pull https://github.com/roshannaik/storm STORM-1956 Alternatively

[jira] [Commented] (STORM-1956) Disable Backpressure by default

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

[jira] [Updated] (STORM-1694) Kafka Spout Trident Implementation Using New Kafka Consumer API

[ https://issues.apache.org/jira/browse/STORM-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-1694: -- Summary: Kafka Spout Trident Implementation Using New Kafka Consumer API (was: TridentKafkaSpout using

[GitHub] storm issue #1500: STORM-1913: Additions and Improvements for Trident RAS AP...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1500 @knusbaum Please rebase and squash the commits before merging. It would be better to have meaningful log message. --- If your project is set up for it, you can reply to this email and have your

[jira] [Commented] (STORM-1913) Additions and Improvements for Trident RAS API

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

[GitHub] storm issue #1546: Storm 1924: Adding conf options for Persistent Word Count...

Github user harshach commented on the issue: https://github.com/apache/storm/pull/1546 +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 #1546: Storm 1924: Adding conf options for Persistent Word Count...

Github user csivaguru commented on the issue: https://github.com/apache/storm/pull/1546 @harshach I have updated the PR to fix the commit message. --- 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

[jira] [Comment Edited] (STORM-1940) Storm Topo is auto re-balance after ZK RECONNECTED

[ https://issues.apache.org/jira/browse/STORM-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368730#comment-15368730 ] happylu edited comment on STORM-1940 at 7/8/16 11:41 PM: - Not very easy, we can

[jira] [Commented] (STORM-1940) Storm Topo is auto re-balance after ZK RECONNECTED

[ https://issues.apache.org/jira/browse/STORM-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368730#comment-15368730 ] happylu commented on STORM-1940: Not very easy, we can only see it each a month, usually compare with ZK

[jira] [Commented] (STORM-1913) Additions and Improvements for Trident RAS API

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

[GitHub] storm issue #1500: STORM-1913: Additions and Improvements for Trident RAS AP...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1500 @d2r Nope, since I don't have background on RAS implementation yet. Please go ahead. --- 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-1924) Add a config file parameter to HDFS test topologies

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

[jira] [Updated] (STORM-1956) Disable Backpressure by default

[ https://issues.apache.org/jira/browse/STORM-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roshan Naik updated STORM-1956: --- Priority: Blocker (was: Major) > Disable Backpressure by default > --- >

[jira] [Updated] (STORM-1956) Disable Backpressure by default

[ https://issues.apache.org/jira/browse/STORM-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roshan Naik updated STORM-1956: --- Fix Version/s: 1.0.2 > Disable Backpressure by default > --- > >

[GitHub] storm issue #1546: Storm 1924: Adding conf options for Persistent Word Count...

Github user harshach commented on the issue: https://github.com/apache/storm/pull/1546 @csivaguru can you update the commit messages there it looks like an internal bug-id in the message. Please add the STORM-1924 in the commit message . --- If your project is set up for it, you

[jira] [Commented] (STORM-1949) Backpressure can cause spout to stop emitting and stall topology

[ https://issues.apache.org/jira/browse/STORM-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368640#comment-15368640 ] Roshan Naik commented on STORM-1949: Have not worked out a concrete solution to avoiding ZK as yet.

[jira] [Created] (STORM-1956) Disable Backpressure by default

Roshan Naik created STORM-1956: -- Summary: Disable Backpressure by default Key: STORM-1956 URL: https://issues.apache.org/jira/browse/STORM-1956 Project: Apache Storm Issue Type: Bug

[jira] [Created] (STORM-1955) Consider implementing Tool + ToolRunner for topologies

Raghav Kumar Gautam created STORM-1955: -- Summary: Consider implementing Tool + ToolRunner for topologies Key: STORM-1955 URL: https://issues.apache.org/jira/browse/STORM-1955 Project: Apache

[jira] [Commented] (STORM-1096) UI tries to impersonate wrong user when getting topology conf for authorization, impersonation is allowed by default

[ https://issues.apache.org/jira/browse/STORM-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368572#comment-15368572 ] Robert Joseph Evans commented on STORM-1096: realPrincipal is the actual user making the

[jira] [Commented] (STORM-1949) Backpressure can cause spout to stop emitting and stall topology

[ https://issues.apache.org/jira/browse/STORM-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368525#comment-15368525 ] Robert Joseph Evans commented on STORM-1949: [~roshan_naik], When writing to ZK every 100 ms

[jira] [Commented] (STORM-1954) Large Trident topologies can cause memory issues due to DefaultResourceDeclarer object reading config

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

[GitHub] storm pull request #1547: STORM-1954: Large Trident topologies can cause mem...

GitHub user knusbaum opened a pull request: https://github.com/apache/storm/pull/1547 STORM-1954: Large Trident topologies can cause memory issues due to DefaultResourceDeclarer object reading config You can merge this pull request into a Git repository by running: $ git

[jira] [Updated] (STORM-1954) Large Trident topologies can cause memory issues due to DefaultResourceDeclarer object reading config

[ https://issues.apache.org/jira/browse/STORM-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Nusbaum updated STORM-1954: Summary: Large Trident topologies can cause memory issues due to DefaultResourceDeclarer object

[jira] [Updated] (STORM-1954) Large Trident topologies can cause memory issues due to Node object reading config

[ https://issues.apache.org/jira/browse/STORM-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Nusbaum updated STORM-1954: Description: DefaultResourceDeclarer objects each read the full config on instantiation. We've

[jira] [Commented] (STORM-1096) UI tries to impersonate wrong user when getting topology conf for authorization, impersonation is allowed by default

[ https://issues.apache.org/jira/browse/STORM-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368476#comment-15368476 ] Sriharsha Chintalapani commented on STORM-1096: --- [~revans2] Thanks for the reply. so in your

[jira] [Commented] (STORM-1949) Backpressure can cause spout to stop emitting and stall topology

[ https://issues.apache.org/jira/browse/STORM-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368473#comment-15368473 ] Sriharsha Chintalapani commented on STORM-1949: --- +1. Given that there are few issues we

[jira] [Comment Edited] (STORM-1949) Backpressure can cause spout to stop emitting and stall topology

[ https://issues.apache.org/jira/browse/STORM-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368451#comment-15368451 ] Roshan Naik edited comment on STORM-1949 at 7/8/16 8:53 PM: [~revans2] Not

[jira] [Comment Edited] (STORM-1949) Backpressure can cause spout to stop emitting and stall topology

[ https://issues.apache.org/jira/browse/STORM-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368451#comment-15368451 ] Roshan Naik edited comment on STORM-1949 at 7/8/16 8:50 PM: [~revans2] Not

[jira] [Commented] (STORM-1949) Backpressure can cause spout to stop emitting and stall topology

[ https://issues.apache.org/jira/browse/STORM-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368451#comment-15368451 ] Roshan Naik commented on STORM-1949: [~revans2] Not sure what you mean by "back on the write" .. are u

[jira] [Commented] (STORM-1096) UI tries to impersonate wrong user when getting topology conf for authorization, impersonation is allowed by default

[ https://issues.apache.org/jira/browse/STORM-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368287#comment-15368287 ] Robert Joseph Evans commented on STORM-1096: [~sriharsha] Sorry I have been out a lot lately

[jira] [Created] (STORM-1954) Large Trident topologies can cause memory issues due to Node object reading config

Kyle Nusbaum created STORM-1954: --- Summary: Large Trident topologies can cause memory issues due to Node object reading config Key: STORM-1954 URL: https://issues.apache.org/jira/browse/STORM-1954

[jira] [Commented] (STORM-1916) Add ability for worker-first classpath

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

[GitHub] storm issue #1507: STORM-1916: Add ability for worker-first classpath

Github user d2r commented on the issue: https://github.com/apache/storm/pull/1507 New test looks good. Build failures (one netty timeout, one windowed executor test failure) look unrelated to this change. Looks like the only thing left to do is change the names of

[jira] [Commented] (STORM-1913) Additions and Improvements for Trident RAS API

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

[GitHub] storm issue #1500: STORM-1913: Additions and Improvements for Trident RAS AP...

Github user d2r commented on the issue: https://github.com/apache/storm/pull/1500 +1 looks good to me. @HeartSaVioR any other comments? --- 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

Re: Request for reviewing

Thanks Juntaek, I finally got some time to review it. Regarding the 1.0.2 release, there are a few open/in-progress issues remaining, but I think we should be in a position to cut a new RC sometime next week. -Taylor > On Jul 8, 2016, at 7:43 AM, Jungtaek Lim wrote: > >

[jira] [Commented] (STORM-1949) Backpressure can cause spout to stop emitting and stall topology

[ https://issues.apache.org/jira/browse/STORM-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367799#comment-15367799 ] Robert Joseph Evans commented on STORM-1949: We have a backup on the write where we will poll

[jira] [Commented] (STORM-1934) Race condition between sync-supervisor and sync-processes raises several strange issues

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

[jira] [Commented] (STORM-1946) ShellBolt.java - On busy system BoltHeartbeatTimerTask fires before setHeartbeat() is executed

[ https://issues.apache.org/jira/browse/STORM-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367705#comment-15367705 ] Slava Andreyev commented on STORM-1946: --- Great. Thanks for taking care of it so fast. >

[jira] [Commented] (STORM-1952) Keeping topology code for supervisor until topology got killed

[ https://issues.apache.org/jira/browse/STORM-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367670#comment-15367670 ] Robert Joseph Evans commented on STORM-1952: We do some of that already with the distributed

[jira] [Commented] (STORM-1910) One topology can't use hdfs spout to read from two locations

[ https://issues.apache.org/jira/browse/STORM-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367664#comment-15367664 ] Robert Joseph Evans commented on STORM-1910: I like the way that beam does this on a lot of

[jira] [Commented] (STORM-1942) Extra closing div tag in topology.html

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

[GitHub] storm issue #1537: STORM-1942: remove extra div that was causing weird margi...

Github user abellina commented on the issue: https://github.com/apache/storm/pull/1537 @priyank5485 mind taking a look at this one? --- 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

[GitHub] storm issue #1536: Storm 1890 ensure we refetch static resources after packa...

Github user abellina commented on the issue: https://github.com/apache/storm/pull/1536 @knusbaum @kishorvpatil @HeartSaVioR could you take a look at this PR? This will help with Storm UI caching issues in browsers. The build failures are unrelated. --- If your project is set up

[jira] [Commented] (STORM-1922) Supervisor summary default order by host

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

[GitHub] storm issue #1519: STORM-1922: Supervisor summary default order by host

Github user vesense commented on the issue: https://github.com/apache/storm/pull/1519 @HeartSaVioR Can you merge this into 1.0.2 too? --- 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

Request for reviewing

Hi devs, I've a pull request for a critical issue, and the patch modifies the heart of supervisor code, so I'd like to make my patch get reviewed by more people in community. STORM-1934: Race condition between sync-supervisor and sync-processes raises several strange issues

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

[ https://issues.apache.org/jira/browse/STORM-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1742. - Resolution: Fixed Fix Version/s: 1.1.0 2.0.0 Merged to master, and 1.x

[jira] [Commented] (STORM-1940) Storm Topo is auto re-balance after ZK RECONNECTED

[ https://issues.apache.org/jira/browse/STORM-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367520#comment-15367520 ] Jungtaek Lim commented on STORM-1940: - [~happylu] Sorry but I don't understand it since ser is not

[jira] [Updated] (STORM-118) Docs: Minor typo in transactional-commit-flow.png

[ https://issues.apache.org/jira/browse/STORM-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-118: --- Fix Version/s: (was: 1.0.2) > Docs: Minor typo in transactional-commit-flow.png >

[jira] [Updated] (STORM-1895) blobstore replication-factor argument

[ https://issues.apache.org/jira/browse/STORM-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1895: Fix Version/s: (was: 1.0.2) > blobstore replication-factor argument >

[jira] [Resolved] (STORM-118) Docs: Minor typo in transactional-commit-flow.png

[ https://issues.apache.org/jira/browse/STORM-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-118. Resolution: Fixed Fix Version/s: 1.0.2 1.0.1 2.0.0

[jira] [Resolved] (STORM-1633) Document "storm blobstore" to command-line-client.md

[ https://issues.apache.org/jira/browse/STORM-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1633. - Resolution: Fixed Fix Version/s: 1.0.1 2.0.0 1.0.0

[jira] [Resolved] (STORM-1895) blobstore replication-factor argument

[ https://issues.apache.org/jira/browse/STORM-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1895. - Resolution: Fixed Fix Version/s: 1.0.2 1.0.1 2.0.0

[jira] [Commented] (STORM-1895) blobstore replication-factor argument

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

[GitHub] storm pull request #1477: [STORM-1895] Blob Store replication-factor argumen...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1477 --- 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-118) Docs: Minor typo in transactional-commit-flow.png

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

[GitHub] storm pull request #1503: STORM-118: Docs: typo in transactional-commit-flow...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1503 --- 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 #1502: STORM-1633: Document blobstore to command-line-cli...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1502 --- 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-1633) Document "storm blobstore" to command-line-client.md

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

[jira] [Resolved] (STORM-1834) Documentation How to Generate Certificates For Local Testing SSL Setup

[ https://issues.apache.org/jira/browse/STORM-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1834. - Resolution: Fixed Fix Version/s: 1.1.0 1.0.2 0.10.2

[jira] [Commented] (STORM-1834) Documentation How to Generate Certificates For Local Testing SSL Setup

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

[GitHub] storm pull request #1414: STORM-1834: Documentation How to Generate Certific...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1414 --- 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-1940) Storm Topo is auto re-balance after ZK RECONNECTED

[ https://issues.apache.org/jira/browse/STORM-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367450#comment-15367450 ] happylu commented on STORM-1940: [~kabhwan] I debug the code and find

[jira] [Resolved] (STORM-1899) Release HBase connection when topology shutdown

[ https://issues.apache.org/jira/browse/STORM-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1899. - Resolution: Fixed Fix Version/s: 1.1.0 1.0.2 2.0.0

[jira] [Commented] (STORM-1899) Release HBase connection when topology shutdown

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

[GitHub] storm pull request #1485: [STORM-1899] Release HBase connection when topolog...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1485 --- 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] [Resolved] (STORM-1844) Some tests are flaky due to low timeout

[ https://issues.apache.org/jira/browse/STORM-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1844. - Resolution: Fixed Fix Version/s: 1.1.0 1.0.2 2.0.0

[GitHub] storm pull request #1421: STORM-1844: Make netty unit test use STORM_TEST_TI...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1421 --- 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 #1452: Python 3 print statement error

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1452 Thanks @Darkless012, I merged into master, 1.x, 1.0.x branch so it'll be reflected to upcoming 1.0.2. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] storm pull request #1452: Python 3 print statement error

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1452 --- 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] [Resolved] (STORM-1919) Introduce FilterBolt on storm-redis

[ https://issues.apache.org/jira/browse/STORM-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1919. - Resolution: Fixed Fix Version/s: 1.1.0 2.0.0 Merged into master and

[jira] [Commented] (STORM-1919) Introduce FilterBolt on storm-redis

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

[GitHub] storm pull request #1517: STORM-1919 Introduce FilterBolt on storm-redis

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1517 --- 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 #1539: 1.x branch

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1539 --- 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-1742) More accurate 'complete latency'

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

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

Github user HeartSaVioR closed the pull request at: https://github.com/apache/storm/pull/1379 --- 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] [Commented] (STORM-1742) More accurate 'complete latency'

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

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

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1379 Already merged by 7029ba951f61bfb2b1608832fa893aaa94fc5732. --- 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

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

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1379 got +1 from PR for master. addressed performance test so I assume it's good to merge. --- 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-1742) More accurate 'complete latency'

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

[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=15367368#comment-15367368 ] ASF GitHub Bot commented on STORM-1742: --- Github user asfgit closed the pull request at:

[GitHub] storm pull request #1523: STORM-1742 More accurate 'complete latency'

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1523 --- 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] [Created] (STORM-1953) [storm-redis] Revisit Mappers to structurize and deprecate/remove unneeded methods

Jungtaek Lim created STORM-1953: --- Summary: [storm-redis] Revisit Mappers to structurize and deprecate/remove unneeded methods Key: STORM-1953 URL: https://issues.apache.org/jira/browse/STORM-1953

[jira] [Resolved] (STORM-1946) ShellBolt.java - On busy system BoltHeartbeatTimerTask fires before setHeartbeat() is executed

[ https://issues.apache.org/jira/browse/STORM-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1946. - Resolution: Fixed Assignee: Slava Andreyev Fix Version/s: 1.1.0

[jira] [Commented] (STORM-1946) ShellBolt.java - On busy system BoltHeartbeatTimerTask fires before setHeartbeat() is executed

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

[GitHub] storm pull request #1542: STORM-1946: initialize lastHeartbeatTimestamp befo...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1542 --- 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-1950) Change response json of "Topology Lag" REST API to keyed by spoutId, topic, partition

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

[GitHub] storm issue #1545: STORM-1950 Change response json of "Topology Lag" REST AP...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1545 Actually I created branch for 1.x, but since the diff is same, I don't create individual pull request for 1.x. I guess we can just cherry-pick to port back. Please let me know if

[jira] [Commented] (STORM-1950) Change response json of "Topology Lag" REST API to keyed by spoutId, topic, partition

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

[GitHub] storm pull request #1545: STORM-1950 Change response json of "Topology Lag" ...

GitHub user HeartSaVioR opened a pull request: https://github.com/apache/storm/pull/1545 STORM-1950 Change response json of "Topology Lag" REST API to keyed by spoutId, topic, partition * bin/storm-kafka-monitor: guard classpath to only uses storm-kafka-monitor*.jar *

[jira] [Resolved] (STORM-1945) Internal Server Error shown on topology page for topology using KafkaSpout

[ https://issues.apache.org/jira/browse/STORM-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1945. - Resolution: Fixed Fix Version/s: 1.1.0 2.0.0 Merged into master and

[jira] [Commented] (STORM-1945) Internal Server Error shown on topology page for topology using KafkaSpout

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

[jira] [Commented] (STORM-1945) Internal Server Error shown on topology page for topology using KafkaSpout

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

[GitHub] storm pull request #1541: STORM-1945 Fix NPE bugs on topology spout lag for ...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1541 --- 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 #1540: STORM-1945 Fix NPE bugs on topology spout lag for ...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1540 --- 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 #1540: STORM-1945 Fix NPE bugs on topology spout lag for storm-k...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1540 Already got +1 from 1.x branch PR and diff is same. 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

[jira] [Commented] (STORM-1945) Internal Server Error shown on topology page for topology using KafkaSpout

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

  1   2   >