Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 4 Nov 2014 23:22:34 +0000 (UTC)
From: "Srimanth Gunturi (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12751820.1414710133000.416429.1415143354728@Atlassian.JIRA>
In-Reply-To: <JIRA.12751820.1414710133000@Atlassian.JIRA>
References: <JIRA.12751820.1414710133000@Atlassian.JIRA>
 <JIRA.12751820.1414710133047@arcas>
Subject: [jira] [Commented] (AMBARI-8055) Alerts UI: Create model and mapper
 for Alert-Notifications
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Srimanth Gunturi commented on AMBARI-8055:
------------------------------------------

+1 for patch.

> Alerts UI: Create model and mapper for Alert-Notifications
> ----------------------------------------------------------
>
>                 Key: AMBARI-8055
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8055
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Xi Wang
>            Assignee: Xi Wang
>              Labels: Alerts-UI
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8055-new.patch, AMBARI-8055.patch
>
>
> Alert notifications will be used by Alert definition and host level alert pages. For them we need to know more details about the notifications that were used. 
> We need a model and mapper created for Alert Notifications. We need to refer to the API to see what exact fields have to mapped.
> {{Alert-Target}} class is:
> * id (number),
> * name: (string),
> * type: (string),  // notification type 'EMAIL' ...
> * description: (string),
> * properties: (string)


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