[
https://issues.apache.org/jira/browse/STORM-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155869#comment-15155869
]
John Fang commented on STORM-1562:
----------------------------------
We can add ITopologyHook which can do a lot of monitor actions to Nimbus, the
hook contains ISubmitterHook.
> Provide a pluggable ability to capture topology information on Nimbus
> (ISubmitterHook on Nimbus)
> ------------------------------------------------------------------------------------------------
>
> Key: STORM-1562
> URL: https://issues.apache.org/jira/browse/STORM-1562
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Hemanth Yamijala
> Priority: Critical
>
> ISubmitterHook was introduced in Storm to enable a pluggable way of capturing
> information submitted in a topology. One use case which we have used it for
> is to capture metadata information and publish to governance stores like
> Apache Atlas. This works quite well for the intended use case.
> However, the fact that this runs on the client mode opens up the possibility
> that the configs for the hook can be overridden by a user either
> inadvertently or with malicious intent. Either is a problem from a use case
> such as governance. It feels that a client side solution would always be
> exposed to this problem. This JIRA is to discuss whether this can be moved to
> the Nimbus side where there would be more control administratively.
> It is understood that moving such a plugin to Nimbus could add its own share
> of issues - hopefully we would be able to discuss and work through them, on
> the assumption that the use case is valid.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
