Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/455#issuecomment-78082542
Turns out that @kishorvpatil found a bug in this during some testing and
should be putting up a fixed pull request shortly.
---
If your project is set up for it, you can
[
https://issues.apache.org/jira/browse/STORM-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357075#comment-14357075
]
ASF GitHub Bot commented on STORM-625:
--
Github user revans2 commented on the pull requ
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/396#issuecomment-78354003
@revans2 not quite comfortable with exposing pid on UI. UI is supposed to
be available for all the users. In non-secure env it can be run without any
filter so I am again
Welcome aboard, Thomas! :-)
--Michael
> On 10.03.2015, at 19:07, P. Taylor Goetz wrote:
>
> Please join me in welcoming Thomas Becker (wurstmeister) as a new Apache
> Storm Committer/PMC member.
>
> Thomas has made significant contributions to the Storm codebase, particularly
> in the area
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xin Wang updated STORM-643:
---
Priority: Minor (was: Critical)
> KafkaUtils repeat fetch messages which offset is out of range
>
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/445#issuecomment-78291244
@revans2 pinging for a review. Thanks.
---
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 do
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/445#issuecomment-78300710
+1. I think most users would much rather define a nimbus.groups m e can
probably file a separate jira for that.
---
If your project is set up for it, you can rep
[
https://issues.apache.org/jira/browse/STORM-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357139#comment-14357139
]
ASF GitHub Bot commented on STORM-689:
--
Github user Parth-Brahmbhatt commented on the
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/414#discussion_r26229576
--- Diff: storm-core/src/clj/backtype/storm/converter.clj ---
@@ -0,0 +1,200 @@
+(ns backtype.storm.converter
--- End diff --
I think it is OK
[
https://issues.apache.org/jira/browse/STORM-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357176#comment-14357176
]
ASF GitHub Bot commented on STORM-634:
--
Github user revans2 commented on a diff in the
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/414#discussion_r26231202
--- Diff: storm-core/src/storm.thrift ---
@@ -243,6 +244,55 @@ struct SubmitOptions {
2: optional Credentials creds;
}
+struct SupervisorI
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/414#issuecomment-78313719
For the most part it looks good. I had a few minor comments. My only real
concern is about maintaining backwards compatibility for clients. I didn't see
much that would
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/436#discussion_r26235414
--- Diff: storm-core/src/genthrift.sh ---
@@ -17,6 +17,16 @@
rm -rf gen-javabean gen-py py
rm -rf jvm/backtype/storm/generated
thrift7 --gen java
[
https://issues.apache.org/jira/browse/STORM-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357307#comment-14357307
]
ASF GitHub Bot commented on STORM-469:
--
Github user revans2 commented on the pull requ
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/388
---
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 enabl
[
https://issues.apache.org/jira/browse/STORM-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357376#comment-14357376
]
ASF GitHub Bot commented on STORM-638:
--
Github user revans2 commented on a diff in the
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/396#discussion_r26242766
--- Diff: storm-core/src/ui/public/templates/component-page-template.html
---
@@ -211,6 +216,7 @@
{{uptime}}
{{host}}
{{
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/422#discussion_r26250879
--- Diff: pom.xml ---
@@ -521,12 +521,6 @@
test
-org.clojars.runa
-
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/421#issuecomment-78360046
+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 w
[
https://issues.apache.org/jira/browse/STORM-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-670.
---
Resolution: Fixed
Fix Version/s: 0.10.0
Thanks [~ptgoetz],
I merged this into m
Suggest we pull in STORM-559 as well. It is strictly an update to
documentation and has already been merged to trunk.
-Original Message-
From: P. Taylor Goetz [mailto:ptgo...@gmail.com]
Sent: Wednesday, March 11, 2015 4:51 PM
To: dev@storm.apache.org
Subject: Re: [DISCUSS] Release Storm
[
https://issues.apache.org/jira/browse/STORM-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358844#comment-14358844
]
Sriharsha Chintalapani commented on STORM-650:
--
Thanks for summarizing [~wurst
+1 for releasing 0.9.4
Thomas
On 11 March 2015 at 21:39, Richard Kellogg wrote:
> Suggest we pull in STORM-559 as well. It is strictly an update to
> documentation and has already been merged to trunk.
>
> -Original Message-
> From: P. Taylor Goetz [mailto:ptgo...@gmail.com]
> Sent: We
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/448
---
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 enabl
[
https://issues.apache.org/jira/browse/STORM-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358985#comment-14358985
]
ASF GitHub Bot commented on STORM-446:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-496.
--
Resolution: Fixed
> task.clj missing debug for logging spout and bolt emit values
[
https://issues.apache.org/jira/browse/STORM-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359194#comment-14359194
]
ASF GitHub Bot commented on STORM-634:
--
Github user Parth-Brahmbhatt commented on the
Github user Parth-Brahmbhatt commented on a diff in the pull request:
https://github.com/apache/storm/pull/414#discussion_r26334368
--- Diff:
storm-core/src/jvm/backtype/storm/serialization/DefaultSerializationDelegate.java
---
@@ -17,11 +17,7 @@
*/
package backtype.sto
[
https://issues.apache.org/jira/browse/STORM-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359192#comment-14359192
]
ASF GitHub Bot commented on STORM-634:
--
Github user Parth-Brahmbhatt commented on a di
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/414#issuecomment-78574474
@revans2 All comments addressed and I really appreciate the time you are
taking to review this.
---
If your project is set up for it, you can reply to this emai
GitHub user harshach opened a pull request:
https://github.com/apache/storm/pull/464
STORM-615. Add REST API to upload topology.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/harshach/incubator-storm STORM-615-V2
Alternatively
[
https://issues.apache.org/jira/browse/STORM-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359397#comment-14359397
]
ASF GitHub Bot commented on STORM-615:
--
GitHub user harshach opened a pull request:
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/414#issuecomment-78618488
@revans2 I agree that it would be great to test forward/backward
compatibility, but testing that in an automated way would be really difficult
since it would likely requir
[
https://issues.apache.org/jira/browse/STORM-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359420#comment-14359420
]
ASF GitHub Bot commented on STORM-634:
--
Github user ptgoetz commented on the pull requ
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/445#issuecomment-78663596
@Parth-Brahmbhatt @revans2 Thanks for the review. I updated the PR to
include nimbus.groups as well and added doc under SECURITY.md. Please take a
look.
---
If your pro
[
https://issues.apache.org/jira/browse/STORM-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359557#comment-14359557
]
ASF GitHub Bot commented on STORM-689:
--
Github user harshach commented on the pull req
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/445#issuecomment-78667664
+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
ena
[
https://issues.apache.org/jira/browse/STORM-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359564#comment-14359564
]
ASF GitHub Bot commented on STORM-689:
--
Github user Parth-Brahmbhatt commented on the
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/437
---
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 enabl
[
https://issues.apache.org/jira/browse/STORM-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359579#comment-14359579
]
ASF GitHub Bot commented on STORM-682:
--
Github user asfgit closed the pull request at:
Jungtaek Lim created STORM-704:
--
Summary: Apply Travis CI
Key: STORM-704
URL: https://issues.apache.org/jira/browse/STORM-704
Project: Apache Storm
Issue Type: Improvement
Environment:
[
https://issues.apache.org/jira/browse/STORM-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359730#comment-14359730
]
Jungtaek Lim edited comment on STORM-704 at 3/13/15 1:12 AM:
-
I
[
https://issues.apache.org/jira/browse/STORM-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim reassigned STORM-704:
--
Assignee: Jungtaek Lim
> Apply Travis CI
> ---
>
> Key: STORM-704
>
[
https://issues.apache.org/jira/browse/STORM-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359730#comment-14359730
]
Jungtaek Lim commented on STORM-704:
I'm trying this now.
> Apply Travis CI
>
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/432#issuecomment-78750701
@atdixon @revans2 with this patch can a user who doesn't want use exhibitor
avoid it by not having the config or the user must have the config in their
storm.yaml.
---
[
https://issues.apache.org/jira/browse/STORM-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359806#comment-14359806
]
ASF GitHub Bot commented on STORM-702:
--
Github user harshach commented on the pull req
Github user caofangkun commented on a diff in the pull request:
https://github.com/apache/storm/pull/422#discussion_r26361833
--- Diff: pom.xml ---
@@ -521,12 +521,6 @@
test
-org.clojars.runa
-
[
https://issues.apache.org/jira/browse/STORM-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359836#comment-14359836
]
ASF GitHub Bot commented on STORM-541:
--
Github user caofangkun commented on a diff in
Github user atdixon commented on the pull request:
https://github.com/apache/storm/pull/432#issuecomment-78764060
The config is optional. If not present, everything works as usual.
On Thu, Mar 12, 2015 at 9:18 PM, Harsha wrote:
> @atdixon @revans2 with this patch can
[
https://issues.apache.org/jira/browse/STORM-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359840#comment-14359840
]
ASF GitHub Bot commented on STORM-702:
--
Github user atdixon commented on the pull requ
Github user caofangkun commented on a diff in the pull request:
https://github.com/apache/storm/pull/296#discussion_r26362192
--- Diff: storm-core/src/clj/backtype/storm/util.clj ---
@@ -392,6 +392,15 @@
(.addArgument command a))
(.execute (DefaultExecutor.) comm
[
https://issues.apache.org/jira/browse/STORM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359847#comment-14359847
]
ASF GitHub Bot commented on STORM-532:
--
Github user caofangkun commented on a diff in
Github user caofangkun commented on a diff in the pull request:
https://github.com/apache/storm/pull/396#discussion_r26362269
--- Diff: storm-core/src/storm.thrift ---
@@ -205,7 +205,8 @@ struct ExecutorSummary {
2: required string component_id;
3: required string host
[
https://issues.apache.org/jira/browse/STORM-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359852#comment-14359852
]
ASF GitHub Bot commented on STORM-638:
--
Github user caofangkun commented on a diff in
Github user vesense commented on the pull request:
https://github.com/apache/storm/pull/445#issuecomment-78814683
+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 w
[
https://issues.apache.org/jira/browse/STORM-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359973#comment-14359973
]
ASF GitHub Bot commented on STORM-689:
--
Github user vesense commented on the pull requ
[
https://issues.apache.org/jira/browse/STORM-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359987#comment-14359987
]
Jungtaek Lim commented on STORM-704:
It's first success build of Apache Storm from Trav
[
https://issues.apache.org/jira/browse/STORM-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-704:
---
Comment: was deleted
(was: It's first success build of Apache Storm from Travis CI.
[https://travis-ci
[
https://issues.apache.org/jira/browse/STORM-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359994#comment-14359994
]
Jungtaek Lim commented on STORM-704:
Sorry I have mistaken. egrep consumes maven's retu
[
https://issues.apache.org/jira/browse/STORM-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-704:
---
Description:
Now Apache Storm takes advantage of Github, we can apply Travis CI to some more
advantage
Github user 2new commented on the pull request:
https://github.com/apache/storm/pull/405#issuecomment-78835043
+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 wish
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360022#comment-14360022
]
ASF GitHub Bot commented on STORM-643:
--
Github user 2new commented on the pull request
62 matches
Mail list logo
