[jira] [Commented] (STORM-1888) add description for storm shell command

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

[GitHub] storm pull request #1472: STORM-1888: add description for shell command

GitHub user vesense opened a pull request: https://github.com/apache/storm/pull/1472 STORM-1888: add description for shell command This can be cherry-picked to 1.x-branch. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (STORM-1888) add description for storm shell command

Xin Wang created STORM-1888: --- Summary: add description for storm shell command Key: STORM-1888 URL: https://issues.apache.org/jira/browse/STORM-1888 Project: Apache Storm Issue Type: Improvement

[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=1532#comment-1532 ] ASF GitHub Bot commented on STORM-1865: --- GitHub user vesense opened a pull request:

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

GitHub user vesense opened a pull request: https://github.com/apache/storm/pull/1471 STORM-1865: update command line client document This can be cherry-picked to 1.x-branch. You can merge this pull request into a Git repository by running: $ git pull

[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=15319973#comment-15319973 ] ASF GitHub Bot commented on STORM-1873: --- Github user satishd commented on a diff in the pull

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

Github user satishd commented on a diff in the pull request: https://github.com/apache/storm/pull/1453#discussion_r66190593 --- Diff: storm-core/test/jvm/org/apache/storm/topology/WindowedBoltExecutorTest.java --- @@ -28,19 +28,20 @@ import org.apache.storm.tuple.Tuple;

[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=15319957#comment-15319957 ] ASF GitHub Bot commented on STORM-1873: --- Github user arunmahadevan commented on the issue:

[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 +1 Looks good --- 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-1771) HiveState should flushAndClose before closing old or idle Hive connections

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

[jira] [Resolved] (STORM-1769) Add a test for submitting topologies to local nimbus with STORM_TOPOLOGY_SUBMISSION_NOTIFIER_PLUGIN.

[ https://issues.apache.org/jira/browse/STORM-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana resolved STORM-1769. --- Resolution: Fixed > Add a test for submitting topologies to local nimbus with >

[jira] [Updated] (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 ] Satish Duggana updated STORM-1864: -- Priority: Critical (was: Major) > StormSubmitter should show proper error messages for

[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 ] Satish Duggana resolved STORM-1864. --- Resolution: Fixed > StormSubmitter should show proper error messages for submitter hook >

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

[GitHub] storm pull request #1463: STORM-1887: Fixed help message for set_log_level c...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1463 --- 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-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=15319898#comment-15319898 ] ASF GitHub Bot commented on STORM-1887: --- Github user harshach commented on the issue:

[GitHub] storm issue #1463: STORM-1887: Fixed help message for set_log_level command

Github user harshach commented on the issue: https://github.com/apache/storm/pull/1463 +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-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=15319867#comment-15319867 ] ASF GitHub Bot commented on STORM-1887: --- Github user ptgoetz commented on the issue:

Re: New Committers/PMC Members: John Fang and Abhishek Agarwal

Cons to John & Abhishek! On Wed, Jun 8, 2016 at 6:20 AM, Harsha wrote: > Congrats John & Abhishek ! > > -Harsha > > On Tue, Jun 7, 2016, at 02:14 PM, Aaron.Dossett wrote: > > I second that! > > > > On 6/7/16, 3:12 PM, "Bobby Evans" wrote: > > > >

[GitHub] storm issue #1463: Fixed help message for set_log_level command

Github user falmp commented on the issue: https://github.com/apache/storm/pull/1463 @ptgoetz Not at all. Done. --- 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

Studying the evolution of Storm project

Hi there, I'm a researcher studying software evolution. As part of my current research, I'm studying the implications of migrating an open-source software project to GitHub, for instance, if the project succeed in attracting newcomers. Storm was in my list. To further analyze the impacts of

Re: New Committers/PMC Members: John Fang and Abhishek Agarwal

Congrats John & Abhishek ! -Harsha On Tue, Jun 7, 2016, at 02:14 PM, Aaron.Dossett wrote: > I second that! > > On 6/7/16, 3:12 PM, "Bobby Evans" wrote: > > >Congratulations to both of you. Well deserved. > > - Bobby > > > >On Tuesday, June 7, 2016 3:02 PM,

Re: New Committers/PMC Members: John Fang and Abhishek Agarwal

Congraturations! Welcome both of you, and thanks for the great work. 2016년 6월 8일 (수) 오전 5:12, Bobby Evans 님이 작성: > Congratulations to both of you. Well deserved. > - Bobby > > On Tuesday, June 7, 2016 3:02 PM, P. Taylor Goetz > wrote: > > >

[jira] [Resolved] (STORM-1442) Storm Solr Connector - Improve Commit Strategy API and Documentation

[ https://issues.apache.org/jira/browse/STORM-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz resolved STORM-1442. Resolution: Fixed > Storm Solr Connector - Improve Commit Strategy API and Documentation >

[jira] [Commented] (STORM-1882) Expose TextFileReader public

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

[GitHub] storm issue #1461: [STORM-1882] Expose TextFileReader public

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

Re: New Committers/PMC Members: John Fang and Abhishek Agarwal

Congratulations to both of you.  Well deserved.  - Bobby On Tuesday, June 7, 2016 3:02 PM, P. Taylor Goetz wrote: Please join me in welcoming John Fang and Abhishek Agarwal as a new Apache Storm Committers and PMC members. John and Abhishek have demonstrated a

[GitHub] storm issue #1153: [STORM-1575] fix TwitterSampleSpout NPE on close

Github user ptgoetz commented on the issue: https://github.com/apache/storm/pull/1153 +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] [Commented] (STORM-1575) TwitterSampleSpout throws NPE on close

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

[jira] [Commented] (STORM-1884) In RedisKeyValueState.prepareCommit keys in pendingPrepare should have priority over pendingCommit

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

[GitHub] storm issue #1464: STORM-1884: Prioritize pendingPrepare over pendingCommit

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

New Committers/PMC Members: John Fang and Abhishek Agarwal

Please join me in welcoming John Fang and Abhishek Agarwal as a new Apache Storm Committers and PMC members. John and Abhishek have demonstrated a strong commitment to the Apache Storm community through active participation and mentoring on the Storm mailing lists. They have also authored many

[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=15319230#comment-15319230 ] P. Taylor Goetz commented on STORM-1864: This should be applied to the 1.0.x-branch as well if it

[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=15319174#comment-15319174 ] ASF GitHub Bot commented on STORM-1887: --- Github user falmp commented on the issue:

[jira] [Updated] (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 ] Francisco Lopes updated STORM-1887: --- Description: The help message for the set_log_level command does not have the topology-name

[GitHub] storm issue #1463: Fixed help message for set_log_level command

Github user falmp commented on the issue: https://github.com/apache/storm/pull/1463 Sure: https://issues.apache.org/jira/browse/STORM-1887 --- 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

[jira] [Commented] (STORM-1886) Extend KeyValueState interface with delete method

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

[GitHub] storm pull request #1470: STORM-1886 Extend KeyValueState iface with delete

GitHub user kosii opened a pull request: https://github.com/apache/storm/pull/1470 STORM-1886 Extend KeyValueState iface with delete The patch also provides implementation for delete in RedisKeyValueState and InMemoryKeyValueState. You can merge this pull request into a Git

[jira] [Created] (STORM-1886) Extend KeyValueState interface with delete method

Balazs Kossovics created STORM-1886: --- Summary: Extend KeyValueState interface with delete method Key: STORM-1886 URL: https://issues.apache.org/jira/browse/STORM-1886 Project: Apache Storm

[jira] [Resolved] (STORM-1878) Flux does not handle stateful bolts

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

[jira] [Commented] (STORM-1878) Flux does not handle stateful bolts

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

[GitHub] storm issue #1458: STORM-1878: Flux can now handle IStatefulBolts

Github user arunmahadevan commented on the issue: https://github.com/apache/storm/pull/1458 Thanks @sakanaou merged to master, 1.x and 1.0.x branches. --- 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-1878) Flux does not handle stateful bolts

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

[GitHub] storm pull request #1458: STORM-1878: Flux can now handle IStatefulBolts

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1458 --- 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-1884) In RedisKeyValueState.prepareCommit keys in pendingPrepare should have priority over pendingCommit

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

[GitHub] storm issue #1464: STORM-1884: Prioritize pendingPrepare over pendingCommit

Github user arunmahadevan commented on the issue: https://github.com/apache/storm/pull/1464 +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 #1463: Fixed help message for set_log_level command

Github user vesense commented on the issue: https://github.com/apache/storm/pull/1463 LGTM Can you please file a jira for this? https://issues.apache.org/jira/browse/STORM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.