[
https://issues.apache.org/jira/browse/AMBARI-7540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161077#comment-14161077
]
Hudson commented on AMBARI-7540:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #492 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/492/])
AMBARI-7540 - Alerts: Stack Alerts Should Not Be Merged Into the DB
(jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a42b727260fde066429347f640c4cb1958f712e3)
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/alerts.json
*
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
* ambari-agent/src/test/python/ambari_agent/dummy_files/definitions.json
> 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)
