[
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 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 because of the size of it, and partly because of the large number
of contributions from different individuals. All of the code changes
individually have been reviewed by storm committers before being pulled into
this branch, but I would really like to see at least 2 committers besides
myself give a +1 to pulling this in. I think it would be great to have more
people look at it, but unless they are blocking issues I would prefer that we
file follow up JIRA for them, and get this in so I don't have to keep
maintaining it.
I am +1.
> Secure Multi-tenant Storm
> -------------------------
>
> Key: STORM-216
> URL: https://issues.apache.org/jira/browse/STORM-216
> Project: Apache Storm
> Issue Type: Umbrella
> Reporter: Robert Joseph Evans
>
> Yahoo has working code for a secure multi-tenant storm at
> https://github.com/yahoo/incubator-storm/tree/security
> We should break the code up into individual pieces, review it and pull it in.
> This is to track all of the different parts of that work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
