storm-redis (scheduled to be released at 0.10.0) has one bugfix and one
essential feature PRs.
- bugfix: https://issues.apache.org/jira/browse/STORM-690
-- It fixes connection pool issue.
- feature: https://issues.apache.org/jira/browse/STORM-691
-- It provides basic lookup / persist bolts so I
[
https://issues.apache.org/jira/browse/STORM-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349006#comment-14349006
]
ASF GitHub Bot commented on STORM-496:
--
Github user ptgoetz commented on the pull
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/437#issuecomment-77394892
We may want to consider applying this to the 0.9.x branch as well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/437#issuecomment-77394741
+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
[
https://issues.apache.org/jira/browse/STORM-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349012#comment-14349012
]
ASF GitHub Bot commented on STORM-682:
--
Github user ptgoetz commented on the pull
[
https://issues.apache.org/jira/browse/STORM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349021#comment-14349021
]
ASF GitHub Bot commented on STORM-675:
--
Github user ptgoetz commented on a diff in the
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/434#issuecomment-77397949
+1. The diffs of `storm` vs. `storm.py` are minimal and related to windows
compatibility.
For easy reference, here they are:
```
$ diff -w storm
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/434#issuecomment-77397764
@ptgoetz Thanks for the review. Removed the year from LICENSE.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
[
https://issues.apache.org/jira/browse/STORM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349040#comment-14349040
]
ASF GitHub Bot commented on STORM-675:
--
Github user ptgoetz commented on the pull
Github user ptgoetz commented on a diff in the pull request:
https://github.com/apache/storm/pull/434#discussion_r25876670
--- Diff: bin/storm ---
@@ -1,5 +1,7 @@
-#!/usr/bin/python
-
+#!/bin/bash
+#
+# Copyright 2014 The Apache Software Foundation
--- End
Github user ptgoetz commented on a diff in the pull request:
https://github.com/apache/storm/pull/434#discussion_r25876751
--- Diff: conf/storm-env.sh ---
@@ -0,0 +1,26 @@
+#!/bin/bash
+#
+# Copyright 2014 The Apache Software Foundation
--- End diff --
Same
[
https://issues.apache.org/jira/browse/STORM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349039#comment-14349039
]
ASF GitHub Bot commented on STORM-675:
--
Github user harshach commented on the pull
Iād like to start a discussion for releasing 0.9.4 (maintenance release) and
0.10.0 (security release).
0.9.4 is basically a branch of 0.9.3 with two important bug fixes:
STORM-329: fix cascading Storm failure by improving reconnection
strategy and buffering messages
STORM-130:
I believe the pull request attached to STORM-693
(https://issues.apache.org/jira/browse/STORM-693) warrants inclusion.
Could someone at least merge this into the trunk?
-Original Message-
From: P. Taylor Goetz [mailto:ptgo...@gmail.com]
Sent: Thursday, March 05, 2015 12:38 PM
To:
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/453#issuecomment-77415797
+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
[
https://issues.apache.org/jira/browse/STORM-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349181#comment-14349181
]
ASF GitHub Bot commented on STORM-693:
--
Github user ptgoetz commented on the pull
I agree with Richard, in addition I think we should also include
https://github.com/apache/storm/pull/437 once Nathan is on board with the
changes.
Thanks
Parth
On 3/5/15, 9:56 AM, Richard Kellogg rmkell...@comcast.net wrote:
I believe the pull request attached to STORM-693
[
https://issues.apache.org/jira/browse/STORM-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349092#comment-14349092
]
Oleg Ostashchuk commented on STORM-477:
---
Does it mean, that there is no need to work
[
https://issues.apache.org/jira/browse/STORM-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348968#comment-14348968
]
ASF GitHub Bot commented on STORM-554:
--
Github user asfgit closed the pull request at:
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/446#issuecomment-77394266
+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
[
https://issues.apache.org/jira/browse/STORM-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Derek Dagit resolved STORM-554.
---
Resolution: Fixed
Fix Version/s: (was: 0.9.3-rc2)
0.10.0
Thanks
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/433#issuecomment-77388451
+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
[
https://issues.apache.org/jira/browse/STORM-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348805#comment-14348805
]
Robert Joseph Evans commented on STORM-477:
---
[~oleg.ost],
The file in question
[
https://issues.apache.org/jira/browse/STORM-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated STORM-477:
--
Comment: was deleted
(was: [~oleg.ost],
The file in question is storm in the bin
[
https://issues.apache.org/jira/browse/STORM-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated STORM-477:
--
Comment: was deleted
(was: [~oleg.ost],
The file in question is storm in the bin
[
https://issues.apache.org/jira/browse/STORM-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348837#comment-14348837
]
ASF GitHub Bot commented on STORM-477:
--
GitHub user ppoulosk opened a pull request:
GitHub user ppoulosk opened a pull request:
https://github.com/apache/storm/pull/457
[STORM-477] Add warning for invalid JAVA_HOME
This adds a check in the python script to ensure that JAVA_HOME points to
an installation of storm, and prints an error message if it is not properly
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/414#issuecomment-77511548
@revans2 @harshach @ptgoetz upmerged again, re-generated all files using
thrift- 0.9.2. Appreciate any feedback you guys can provide.
---
If your project is set
[
https://issues.apache.org/jira/browse/STORM-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350011#comment-14350011
]
ASF GitHub Bot commented on STORM-634:
--
Github user Parth-Brahmbhatt commented on the
Hello,
Can Storm be deployed in a topology where the nimbus node and data
nodes in a single cluster can span different data centers (for Disaster
recovery scenarios)? Or is there another recommended deployment topology for DR
scenarios?
Regards
Rama
30 matches
Mail list logo
