Github user Sergeant007 commented on the pull request:
https://github.com/apache/storm/pull/304#issuecomment-62714754
Guys, it there any update on this pull request? As for me, the bug it fixes
is rather critical and the fix is simple enough (without refactoring, etc) to
be merged
[
https://issues.apache.org/jira/browse/STORM-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Zhong updated STORM-537:
-
Assignee: Sergey Tryuber
A worker reconnects infinitely to another dead worker
[
https://issues.apache.org/jira/browse/STORM-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208015#comment-14208015
]
Sean Zhong commented on STORM-537:
--
merged, thanks for your contribution.
A worker
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/304
---
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
[
https://issues.apache.org/jira/browse/STORM-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208060#comment-14208060
]
ASF GitHub Bot commented on STORM-537:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208127#comment-14208127
]
Jungtaek Lim commented on STORM-350:
[~clockfly]
Can I use this jar with
Sorry I have been out of the office for the past two weeks, I would really like
to do it soon. Once I am caught up on e-mail I will do an upmerge, test it,
and then hopefully ask for a vote to merge it in.
- Bobby
On Saturday, November 8, 2014 6:07 PM, Harsha st...@harsha.io wrote:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/306
---
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
[
https://issues.apache.org/jira/browse/STORM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208263#comment-14208263
]
ASF GitHub Bot commented on STORM-546:
--
Github user asfgit closed the pull request at:
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/121#issuecomment-62754593
I think we are at the point where we should merge the security branch into
master. This is a little bit different from most patches/pull requests we have
done, partly
I think the pull request to add authentication and authorization to storm is
now ready to be merged into master.
https://github.com/apache/storm/pull/121#issuecomment-62754593
It is a little different from most pull requests, because of its size and all.
As I said in the comment but I would
Hello All,
I'd appreciate your input/pointers regarding my post on join and in-blot
caching.
thanks,
Clay
On Tue, Nov 11, 2014 at 5:09 AM, clay teahouse clayteaho...@gmail.com
wrote:
Hello All,
I need to
1) Look up some values from a source and cache them in a bolt
2) Filter a second stream
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/121#issuecomment-62758258
I am +1. Feedback on overall security branch we tested it over a period of
time with these merges in with master and there aren't any issues for storm
regular and storm
[
https://issues.apache.org/jira/browse/STORM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208295#comment-14208295
]
ASF GitHub Bot commented on STORM-216:
--
Github user harshach commented on the pull
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/121#issuecomment-62782715
Like I said in the mailing list, I have been out for a few weeks. I didn't
see 0.9.3 go out, but I thought that it must be very close by now. I'll send a
separate mail
[
https://issues.apache.org/jira/browse/STORM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208575#comment-14208575
]
ASF GitHub Bot commented on STORM-216:
--
Github user revans2 commented on the pull
Yes, this type of a feature would be great to have. I am rally curious how you
have done the changes, as there are a lot of potential pitfalls here. At a
minimum it would just be great to have the feedback framework in place so we
can iterate on these changes.
- Bobby
On Wednesday,
[
https://issues.apache.org/jira/browse/STORM-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208843#comment-14208843
]
Sriharsha Chintalapani commented on STORM-473:
--
As per the comments closing
Sure,
The main thing that storm is missing right now is an metrics feedback system to
the scheduler (or possibly a separate piece of code that decides when to
grow/shrink a topology). We have some basic metrics, but they are not exposed
to the scheduler. The other question is how do we deal
[
https://issues.apache.org/jira/browse/STORM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-544:
-
Assignee: P. Taylor Goetz
Some documents from website are outdated
Maybe plus STORM-329 (contains fix for STORM-404 and STORM-510), the fix
version was wrongly marked to 0.92.
It fixed the chained failure of worker crash, also the blocking behavior
when one connection is down.
Let's be ready for the security branch.
On Thu, Nov 13, 2014 at 7:24 AM, Harsha
I'm +1 for merging the security branch to master, we just need a little
coordination.
Tomorrow (EST) I'll create a 0.9.3-branch from the current master. After that
any outstanding pull requests targeting master should be merged to that branch
(obviously +1, etc. rules apply).
That way we can
Github user BuDongDong commented on the pull request:
https://github.com/apache/storm/pull/312#issuecomment-62844422
(defn- get-task-object [^TopologyContext topology component-id] ... ... )
i think the type of param topology is StormTopology not TopologyContext
---
If
GitHub user BuDongDong opened a pull request:
https://github.com/apache/storm/pull/312
Update get-task-object function, change the type of first param
topology from ^TopologyContext to ^StormTopology
update get-task-object function, change the type of first param
topology from
24 matches
Mail list logo
