[
https://issues.apache.org/jira/browse/EAGLE-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649522#comment-15649522
]
ASF GitHub Bot commented on EAGLE-756:
--------------------------------------
GitHub user mizeng opened a pull request:
https://github.com/apache/incubator-eagle/pull/630
EAGLE-756: make sure publish change is sent to runtime bolts
During test with Alert Engine publisher, it looks like when we have slack
publishment, the metadata reload become slow refreshed when use change the
metadata and manually trigger the coordinator schedule.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mizeng/incubator-eagle master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/630.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 #630
----
commit e514041d33868971bc9cc91b1a6ffa53cf7028bd
Author: mizeng <miz...@ebaysf.com>
Date: 2016-11-08T23:37:39Z
EAGLE-756: make sure publish change is sent to runtime bolts
----
> metadata change (with coordinator build) in publishment is not sent to
> runtime bolts
> ------------------------------------------------------------------------------------
>
> Key: EAGLE-756
> URL: https://issues.apache.org/jira/browse/EAGLE-756
> Project: Eagle
> Issue Type: Bug
> Reporter: Zeng, Bryant
> Assignee: Zeng, Bryant
>
> During test Alert Engine publisher,
> it looks like when we have slack publishment, the metadata reload become
> slow refreshed when use change the metadata and manually trigger the
> coordinator schedule.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
