[
https://issues.apache.org/jira/browse/AMBARI-16915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303056#comment-15303056
]
ASF GitHub Bot commented on AMBARI-16915:
-----------------------------------------
GitHub user csivaguru opened a pull request:
https://github.com/apache/ambari/pull/33
AMBARI-16915 Do not set the notifier plugin class property when not
specified in storm defaults
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/csivaguru/ambari AMBARI-16915
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ambari/pull/33.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #33
----
commit b75b53251e2dec6a31bd45b679baf278100ce02c
Author: Sivaguru Kannan <schendamaraikan...@hortonworks.com>
Date: 2016-05-26T22:05:05Z
AMBARI-16915 Do not set the notifier plugin class property when not
specified in storm defaults
----
> Storm Stack advisor should not make
> storm.topology.submission.notifier.plugin.class property required
> -----------------------------------------------------------------------------------------------------
>
> Key: AMBARI-16915
> URL: https://issues.apache.org/jira/browse/AMBARI-16915
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Sivaguru Kannan
>
> The Ambari change, This is in reference with your change,
> https://github.com/apache/ambari/commit/89fd30b40f3108bfcbcc73eb2d74c94a2ba14a7a
> accidentally made the storm.topology.submission.notifier.plugin property
> mandatory.
> If the storm defaults yaml config does not set the property a " " value is
> set for the property. This causes storm startup to fail with a Class Not
> Found exception when starting with Ambari.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
