You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2014/09/29 17:05:34 UTC

[jira] [Created] (AMBARI-7540) Alerts: Stack Alerts Should Not Be Merged Into the DB

Jonathan Hurley created AMBARI-7540:
---------------------------------------

             Summary: Alerts: Stack Alerts Should Not Be Merged Into the DB
                 Key: AMBARI-7540
                 URL: https://issues.apache.org/jira/browse/AMBARI-7540
             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


Initially, it was thought that alerts defined on the stack should be merged into existing alerts in the database on server startup so that changes made to the stack will be updated in the DB.

However, there is a problem with this approach where editing a stack-based alert from the REST endpoints will be overwritten on the next startup. We could track this state change in the database, but this seems like a v2 feature.

For v1, let's change the logic so that stack merging into the DB is only done for new alerts detected in alerts.json.



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