[GitHub] storm pull request #:

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/commit/4d80461a62e6f739dccff79af176bc109bc491e7#commitcomment-18651226 @childnode In order to create release artifacts, release manager should do maven release even though vote is not started.

[jira] [Updated] (STORM-1443) Support customizing parallelism in StormSQL

[ https://issues.apache.org/jira/browse/STORM-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1443: Component/s: storm-sql > Support customizing parallelism in StormSQL >

[jira] [Updated] (STORM-1446) Compile the Calcite logical plan to Storm physical plan

[ https://issues.apache.org/jira/browse/STORM-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1446: Component/s: storm-sql > Compile the Calcite logical plan to Storm physical plan >

[jira] [Updated] (STORM-1435) Build a single jar with dependency for StormSQL dependency

[ https://issues.apache.org/jira/browse/STORM-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1435: Component/s: storm-sql > Build a single jar with dependency for StormSQL dependency >

[jira] [Updated] (STORM-1434) Support the GROUP BY clause in StormSQL

[ https://issues.apache.org/jira/browse/STORM-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1434: Component/s: storm-sql > Support the GROUP BY clause in StormSQL >

[GitHub] storm pull request #:

Github user childnode commented on the pull request: https://github.com/apache/storm/commit/4d80461a62e6f739dccff79af176bc109bc491e7#commitcomment-18651064 @HeartSaVioR thanks for the info perhaps, the https://github.com/apache/storm/releases/tag/v1.1.0 from 15th of july by @ptgoetz

Re: [VOTE] Release Apache Storm 0.9.7 (RC1)

Would it be better to have consensus for this? In bylaw we have this sentence 'In particular all releases must be approved by the PMC.' One of PMC can call out the discussion for releasing specific version, but general consensus should be made before starting prepare release. I'd like to see

[VOTE] Release Apache Storm 0.9.7 (RC1)

This is a call to vote on releasing Apache Storm 0.9.7 (rc1). This release candidate addresses a critical issue with Storm’s multi-lang component where an improperly formed multi-lang spout message would cause the spout to hang indefinitely. Full list of changes in this release:

[GitHub] storm pull request #1627: STORM-2039: backpressure refactoring in worker and...

Github user abellina closed the pull request at: https://github.com/apache/storm/pull/1627 --- 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-2039) Backpressure refactoring in worker and executor

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

[jira] [Commented] (STORM-2039) Backpressure refactoring in worker and executor

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

[GitHub] storm pull request #1627: STORM-2039: backpressure refactoring in worker and...

GitHub user abellina reopened a pull request: https://github.com/apache/storm/pull/1627 STORM-2039: backpressure refactoring in worker and executor For 1.x branch, will submit a PR for 2.x branch. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (STORM-2039) Backpressure refactoring in worker and executor

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

[GitHub] storm pull request #1627: STORM-2039: backpressure refactoring in worker and...

GitHub user abellina opened a pull request: https://github.com/apache/storm/pull/1627 STORM-2039: backpressure refactoring in worker and executor For 1.x branch, will submit a PR for 2.x branch. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Assigned] (STORM-2039) Backpressure refactoring in worker and executor

[ https://issues.apache.org/jira/browse/STORM-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Bellina reassigned STORM-2039: - Assignee: Alessandro Bellina > Backpressure refactoring in worker and executor >

[jira] [Commented] (STORM-1985) Provide a tool for showing and killing corrupted topology

[ https://issues.apache.org/jira/browse/STORM-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421384#comment-15421384 ] Robert Joseph Evans commented on STORM-1985: I would start off with command line, if you are

Re: Storm Development Assistance

Hi Bobby, Thanks for your reply. I would use JIRA for any further discussion on this task. Regards, --Kamal On Mon, Aug 15, 2016 at 6:50 PM, Bobby Evans wrote: > My guess is that this is going to be a new tool. I think we want to start > looking into supporting a

[jira] [Commented] (STORM-1985) Provide a tool for showing and killing corrupted topology

[ https://issues.apache.org/jira/browse/STORM-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421377#comment-15421377 ] Kamlesh Bhatt commented on STORM-1985: -- Hi Bobby, Thanks for answering my query. Does it make

[jira] [Comment Edited] (STORM-2038) Provide an alternative to using symlinks

[ https://issues.apache.org/jira/browse/STORM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421036#comment-15421036 ] Robert Joseph Evans edited comment on STORM-2038 at 8/15/16 2:23 PM: -

[jira] [Commented] (STORM-2038) Provide an alternative to using symlinks

[ https://issues.apache.org/jira/browse/STORM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421036#comment-15421036 ] Robert Joseph Evans commented on STORM-2038: Giving a canonical path to the worker artifacts

[jira] [Commented] (STORM-1985) Provide a tool for showing and killing corrupted topology

[ https://issues.apache.org/jira/browse/STORM-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420963#comment-15420963 ] Robert Joseph Evans commented on STORM-1985: It was asked on the mailing list where this code

Re: Storm Development Assistance

My guess is that this is going to be a new tool.  I think we want to start looking into supporting a storm admin tool that will give users that have access to super user credentials access to directly examine/modify the state of a running storm cluster, zookeeper, blobstore, and local state. I

Storm Development Assistance

Hi All, I am newbie to Storm Community and intend to learn Storm and willing to contribute to Storm development efforts. I have done some initial ground work in terms of going through the contribution documents ( https://storm.apache.org/contribute/Contributing-to-Storm.html). I have also setup

[jira] [Created] (STORM-2038) Provide an alternative to using symlinks

Paul Milliken created STORM-2038: Summary: Provide an alternative to using symlinks Key: STORM-2038 URL: https://issues.apache.org/jira/browse/STORM-2038 Project: Apache Storm Issue Type: