[jira] [Updated] (STORM-1773) Utils.javaDeserialize() doesn't work with primitive types

[ https://issues.apache.org/jira/browse/STORM-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1773: Description: It's based on reporting from user@. Please refer

[jira] [Created] (STORM-1773) Utils.javaDeserialize() doesn't work with primitive types

Jungtaek Lim created STORM-1773: --- Summary: Utils.javaDeserialize() doesn't work with primitive types Key: STORM-1773 URL: https://issues.apache.org/jira/browse/STORM-1773 Project: Apache Storm

[jira] [Commented] (STORM-1772) Create topologies for measuring performance

[ https://issues.apache.org/jira/browse/STORM-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15277540#comment-15277540 ] Manu Zhang commented on STORM-1772: --- Hi [~roshan_naik], Do you mean

[jira] [Commented] (STORM-433) Give users visibility to the depth of queues at each bolt

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

Re: [DISCUSSION] Version lines of 1.x

What I really wanted to address is, I don't want to see us making effort with questioning/deciding this bug should be port back to 0.x, and do actual work by hand (since we change the package name) for each pull request. There will be three branches to concern, and since master and 1.x are

Re: [DISCUSSION] Version lines of 1.x

I think we're in total agreement. I just would like to see 0.10.x remain open for bug fixes and releases. I don't think we should back port new features. -Taylor > On May 9, 2016, at 7:06 PM, Jungtaek Lim wrote: > > Taylor, > > That would be also OK with me. > What I

Re: [DISCUSSION] Version lines of 1.x

Taylor, That would be also OK with me. What I really wanted to address is that I don't see the benefit to give efforts to maintain 0.x version line. In other words, I don't want to backport non-critical bugfix to 0.x version. It should be minimized, but it would be still possible to release new

[jira] [Created] (STORM-1772) Create topologies for measuring performance

Roshan Naik created STORM-1772: -- Summary: Create topologies for measuring performance Key: STORM-1772 URL: https://issues.apache.org/jira/browse/STORM-1772 Project: Apache Storm Issue Type: Bug

[jira] [Updated] (STORM-1772) Create topologies for measuring performance

[ https://issues.apache.org/jira/browse/STORM-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roshan Naik updated STORM-1772: --- Description: Would be very useful to have some simple reference topologies included with Storm that

[jira] [Assigned] (STORM-1772) Create topologies for measuring performance

[ https://issues.apache.org/jira/browse/STORM-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roshan Naik reassigned STORM-1772: -- Assignee: Roshan Naik > Create topologies for measuring performance >

Re: [DISCUSSION] Version lines of 1.x

I’m okay with discontinuing active development on 0.10.x. That being said, I don’t think we should discourage bug fixes against that branch. There will be users on those versions for a long time. I think not too long ago I saw a question from someone who was still on a pre-Apache release. :)

[jira] [Commented] (STORM-1757) Apache Beam Runner for Storm

[ https://issues.apache.org/jira/browse/STORM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15276656#comment-15276656 ] Robert Joseph Evans commented on STORM-1757: [~ptgoetz] and others, I am fine no matter where

[GitHub] storm pull request: STORM-822: Kafka Spout New Consumer API

Github user jianbzhou commented on the pull request: https://github.com/apache/storm/pull/1131#issuecomment-217905885 thanks Hmcl. Just found below log constantly show up, seems it constantly try to commit one offset which is actually committed to kafka already – it might

[jira] [Commented] (STORM-822) Kafka Spout New Consumer API

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

[jira] [Commented] (STORM-1730) LocalCluster#shutdown() does not terminate all storm threads/thread pools.

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

[GitHub] storm pull request: This closes #STORM-1730 #1730 LocalCluster#shu...

Github user kishorvpatil commented on the pull request: https://github.com/apache/storm/pull/1400#issuecomment-217898782 @fbyrne, closing and reopening the PR or adding commit triggers the build. --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Created] (STORM-1771) HiveState should flushAndClose before closing old or idle Hive connections

Sriharsha Chintalapani created STORM-1771: - Summary: HiveState should flushAndClose before closing old or idle Hive connections Key: STORM-1771 URL: https://issues.apache.org/jira/browse/STORM-1771

[jira] [Commented] (STORM-1277) port backtype.storm.daemon.executor to java

[ https://issues.apache.org/jira/browse/STORM-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15276488#comment-15276488 ] Cody commented on STORM-1277: - I've finished most of the code and currently on the integration test, and may

Re: [DISCUSSION] Version lines of 1.x

+1 (non-binding) or maintaining 1.x branch as it is the base for all the package name change and lots of new features. If we have to discontinue a branch, I would also favor discontinuing 0.10.x . Hugo > On May 9, 2016, at 8:06 AM, Bobby Evans wrote: > > +1 for

[jira] [Commented] (STORM-822) Kafka Spout New Consumer API

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

[GitHub] storm pull request: STORM-822: Kafka Spout New Consumer API

Github user hmcl commented on the pull request: https://github.com/apache/storm/pull/1131#issuecomment-217894464 @jianbzhou thanks for your feedback. Let me take a look at this and I will get back to you shortly. --- If your project is set up for it, you can reply to this email and

Re: 答复: [DISCUSSION] Version lines of 1.x

+1 for that too.  We should be on the same page here, but this is non-binding.  The bylaws state that any PMC member can bring up a release for a vote.  - Bobby On Monday, May 9, 2016 8:20 AM, Aaron. Dossett wrote: +1. Same here. On 5/9/16, 5:47 AM, "John

[jira] [Commented] (STORM-1239) port backtype.storm.scheduler.IsolationScheduler to java

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

[GitHub] storm pull request: STORM-1239: port backtype.storm.scheduler.Isol...

Github user vesense commented on a diff in the pull request: https://github.com/apache/storm/pull/1359#discussion_r62511356 --- Diff: storm-core/src/jvm/org/apache/storm/scheduler/IsolationScheduler.java --- @@ -0,0 +1,434 @@ +/** + * Licensed to the Apache Software

[jira] [Commented] (STORM-1239) port backtype.storm.scheduler.IsolationScheduler to java

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

[jira] [Commented] (STORM-1239) port backtype.storm.scheduler.IsolationScheduler to java

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

[GitHub] storm pull request: STORM-1239: port backtype.storm.scheduler.Isol...

Github user vesense commented on the pull request: https://github.com/apache/storm/pull/1359#issuecomment-217887114 Thanks @abhishekagarwal87 Addressed your 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

[GitHub] storm pull request: STORM-1239: port backtype.storm.scheduler.Isol...

Github user vesense commented on a diff in the pull request: https://github.com/apache/storm/pull/1359#discussion_r62511422 --- Diff: storm-core/src/jvm/org/apache/storm/scheduler/IsolationScheduler.java --- @@ -0,0 +1,434 @@ +/** + * Licensed to the Apache Software

[jira] [Commented] (STORM-1239) port backtype.storm.scheduler.IsolationScheduler to java

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

[GitHub] storm pull request: STORM-1239: port backtype.storm.scheduler.Isol...

Github user vesense commented on a diff in the pull request: https://github.com/apache/storm/pull/1359#discussion_r62511320 --- Diff: storm-core/src/jvm/org/apache/storm/scheduler/IsolationScheduler.java --- @@ -0,0 +1,434 @@ +/** + * Licensed to the Apache Software

Re: 答复: [DISCUSSION] Version lines of 1.x

+1. Same here. On 5/9/16, 5:47 AM, "John Fang" wrote: >I'm also think we shouldn't maintain 0.10.x branch > >-邮件原件- >发件人: Cody Innowhere [mailto:e.neve...@gmail.com] >发送时间: 2016年5月9日 19:42 >收件人: dev@storm.apache.org >主题: Re: [DISCUSSION] Version lines of

答复: [DISCUSSION] Version lines of 1.x

I'm also think we shouldn't maintain 0.10.x branch -邮件原件- 发件人: Cody Innowhere [mailto:e.neve...@gmail.com] 发送时间: 2016年5月9日 19:42 收件人: dev@storm.apache.org 主题: Re: [DISCUSSION] Version lines of 1.x I'm also +1 for maintaining 1.x branch & master and not maintaining 0.10.x branch. On

Re: [DISCUSSION] Version lines of 1.x

I'm also +1 for maintaining 1.x branch & master and not maintaining 0.10.x branch. On Mon, May 9, 2016 at 1:04 PM, Abhishek Agarwal wrote: > +1. There is lot development effort pending against 1.x branch which will > get unblocked with 1.1.0 branch. I am assuming, we will

[jira] [Commented] (STORM-1730) LocalCluster#shutdown() does not terminate all storm threads/thread pools.

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

[GitHub] storm pull request: This closes #STORM-1730 #1730 LocalCluster#shu...

Github user fbyrne commented on the pull request: https://github.com/apache/storm/pull/1400#issuecomment-217830423 Does a comment retrigger a build? we'll see. --- 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-433) Give users visibility to the depth of queues at each bolt

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

[GitHub] storm pull request: [STORM-433] [WIP] Executor queue backlog metri...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1406#issuecomment-217794597 For addressing big picture of metrics improvement, yes we want to address four major points. But given that we already released major version of Storm