ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15602) Database Changes to Support Alert Repeat Tolerance
Date Tue, 29 Mar 2016 12:41:25 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-15602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Hurley updated AMBARI-15602:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Database Changes to Support Alert Repeat Tolerance
> --------------------------------------------------
>
>                 Key: AMBARI-15602
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15602
>             Project: Ambari
>          Issue Type: Task
>    Affects Versions: 2.4.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15602.patch
>
>
> The {{alert_definition}} table will be updated to include a nullable column which represents
the custom repeat/retry tolerance value. This value will override that which is set in the
{{cluster-env/alerts_repeat_tolerance}} property.
> {code}
> CREATE TABLE alert_definition (
>   definition_id BIGINT NOT NULL,
>   cluster_id BIGINT NOT NULL,
>   ...
>   repeat_tolerance SMALLINT,
>   repeat_tolerance_enabled TINYINT,
>   ...
>   PRIMARY KEY (definition_id),
>   FOREIGN KEY (cluster_id) REFERENCES clusters(cluster_id),
>   CONSTRAINT uni_alert_def_name UNIQUE(cluster_id,definition_name)
> );
> {code}
> The scope of work includes:
> - SQL File changes
> - Entity changes
> - ResourceProvider changes to expose these values
> - UpgradeCatalog changes
> - Tests



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

Mime
View raw message