[ 
https://issues.apache.org/jira/browse/AMBARI-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161068#comment-14161068
 ] 

Hudson commented on AMBARI-7094:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #492 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/492/])
AMBARI-7094 - Alerts: Implement Property Updates for Alert Targets 
(jonathanhurley) (jhurley: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2f5c78e7f90f575ab2c469da1095eaa5d252d872)
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertTarget.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/parsers/JsonRequestBodyParser.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/resources/AlertDefResourceDefinition.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProviderTest.java
* ambari-server/src/main/java/org/apache/ambari/server/state/ConfigFactory.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/AlertTargetService.java


> Alerts: Implement Property Updates for Alert Targets
> ----------------------------------------------------
>
>                 Key: AMBARI-7094
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7094
>             Project: Ambari
>          Issue Type: Task
>          Components: alerts, ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 2.0.0
>
>
> Alert Targets should have the ability to contain an unstructured set of 
> properties so that customer defined targets (and dispatchers) can still be 
> stored and retrieved by Ambari.
> The initial design had a defined structure for both email and snmp protocols. 
> However, these properties were just turned into a flat set by the data layer. 
> For the initial approach, it doesn't make much sense to try to model 
> structured properties when, at the end of the day, they need to be serialized 
> to a map.
> {code}
> {
>   "AlertTarget": {
>     "name": "Administrators",
>     "description": "The Admins",
>     "notification_type": "EMAIL",
>     "properties":{
>       "mail.smtp.host": "my.host.net",
>       "mail.smtp.port" : "587",
>       ...
>     }
>   }
> }
> {code}
> This also lets any property defined be passed to the backend provider in 
> order to properly dispatch to the targets. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to