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" f
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 your
[
https://issues.apache.org/jira/browse/STORM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209241#comment-14209241
]
ASF GitHub Bot commented on STORM-216:
--
Github user ptgoetz commented on the pull requ
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/121#issuecomment-62839886
I also replied to the list, I'm +1 for merging to master once we create a
0.9.3 branch.
The modifications in the security branch have been QA'd fairly extensively
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
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
[
https://issues.apache.org/jira/browse/STORM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Zhong updated STORM-329:
-
Fix Version/s: (was: 0.9.2-incubating)
0.9.3-rc2
> Add Option to Config Message hand
Thanks for the detailed explanation Bobby. I will keep this in mind when I
create my design document.
I will mostly not deal with adding/removing bolts to the topology and
restrict myself to threads and tasks. This is because of the time I have to
complete the project. Once I submit my report (ear
STORM-386 should be resolved
STORM-350 I think Taylor is working on reproducing the message loss,
I'll try to do the same.
STORM-513 I don't think it should be a blocker. Taylor and Sean already
+1 ed it. I'll take a look at it today and if possible we can get this
in 0.9.3 release.
Jungtaek,
[
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
>
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 wi
[
https://issues.apache.org/jira/browse/STORM-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208850#comment-14208850
]
Sriharsha Chintalapani commented on STORM-531:
--
[~erajabi] [~rahulravipati] Do
I wish STORM-513 to be resolved, because it already has two +1 from
committers, and it can be a blocker to multilang users.
But when we think there needs some more discussions about it, I'm sure it
can be merged to next release, maybe 0.9.4.
(We're having a voice about documentation from PR, #286.)
[
https://issues.apache.org/jira/browse/STORM-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208843#comment-14208843
]
Sriharsha Chintalapani commented on STORM-473:
--
As per the comments closing th
[
https://issues.apache.org/jira/browse/STORM-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-473.
--
Resolution: Won't Fix
> Provide BASH script (storm.sh)
>
Hi Bobby,
Thanks for getting back to me. It is encouraging to hear that this will
be a good addition to Storm if done well.
I have not implemented the changes yet. My project just started. It spans
over the next 2 months. In a few days, I will create a JIRA task and submit
my proposal. It wou
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, No
I have been out and was wondering what the status is of the 0.9.3 release. I
am curious what is blocking us from releasing? This is mostly so that we can
get the security branch merged into master. Looking at JIRA I see that there
are a number of JIRA targeted to 0.9.3 that are reopened or ope
Hi,
It will definitely interesting to the storm community. It will be
great if you can create a JIRA and post your code as PR for others
to try out and review the code.
Thanks,
Harsha
On Wed, Nov 12, 2014, at 11:16 AM, Harsha Balasubramanian wrote:
> Please let me know if my projec
[
https://issues.apache.org/jira/browse/STORM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208575#comment-14208575
]
ASF GitHub Bot commented on STORM-216:
--
Github user revans2 commented on the pull requ
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 t
Please let me know if my project (outlined below) will be useful to Storm.
Thanks,
Harsha
*Contact Details: *
Harsha Balasubramanian
Graduate Student at University of Toronto
Professional Masters in Computer Science
Email 1: harsha...@cs.toronto.edu
Email 2: harsha...@gmail.com
LinkedIn : ca.lin
[
https://issues.apache.org/jira/browse/STORM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208295#comment-14208295
]
ASF GitHub Bot commented on STORM-216:
--
Github user harshach commented on the pull req
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 s
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
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 based on the looke
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 li
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 bec
[
https://issues.apache.org/jira/browse/STORM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208273#comment-14208273
]
ASF GitHub Bot commented on STORM-216:
--
Github user revans2 commented on the pull requ
[
https://issues.apache.org/jira/browse/STORM-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208263#comment-14208263
]
ASF GitHub Bot commented on STORM-546:
--
Github user asfgit closed the pull request at:
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 enabl
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 wrote:
Hi,
D
[
https://issues.apache.org/jira/browse/STORM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208127#comment-14208127
]
Jungtaek Lim commented on STORM-350:
[~clockfly]
Can I use this jar with storm-0.9.2-i
[
https://issues.apache.org/jira/browse/STORM-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208060#comment-14208060
]
ASF GitHub Bot commented on STORM-537:
--
Github user asfgit closed the pull request at:
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 enabl
[
https://issues.apache.org/jira/browse/STORM-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Zhong resolved STORM-537.
--
Resolution: Fixed
Fix Version/s: 0.9.3-rc2
> A worker reconnects infinitely to another dead worker
[
https://issues.apache.org/jira/browse/STORM-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208015#comment-14208015
]
Sean Zhong commented on STORM-537:
--
merged, thanks for your contribution.
> A worker reco
[
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-tabpanel&focusedCommentId=14208012#comment-14208012
]
ASF GitHub Bot commented on STORM-537:
--
Github user Sergeant007 commented on the pull
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 fas
39 matches
Mail list logo
