[
https://issues.apache.org/jira/browse/EAGLE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15540601#comment-15540601
]
ASF GitHub Bot commented on EAGLE-585:
--------------------------------------
GitHub user RalphSu opened a pull request:
https://github.com/apache/incubator-eagle/pull/470
[EAGLE-585] : AlertEngine: create metadata validation api
Author: ralphsu
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/RalphSu/incubator-eagle master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/470.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #470
----
commit f686b37720fe6191644f289f9fc5190efb24d554
Author: Ralph, Su <[email protected]>
Date: 2016-10-02T16:07:12Z
[EAGLE-585] : AlertEngine: create metadata validation api
Author: ralphsu
----
> AlertEngine: create metadata validation api
> -------------------------------------------
>
> Key: EAGLE-585
> URL: https://issues.apache.org/jira/browse/EAGLE-585
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.5.0
> Reporter: Su Ralph
> Assignee: Su Ralph
> Fix For: v0.5.0
>
>
> Currently alert engine metadata are inter connected but without strong
> validation. User usually confused by coordinator build failure or even when
> coordinator build succeed but runtime failure. In deployment with traffic
> runtime exception/error often lost in flood of logs.
> Step1: Provide metadata validation api so user is able to verify the metadata
> before push data.
> Step2: do more validation during coordinator build.
> This issue to track step1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
