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

Posted to issues@eagle.apache.org by "Jayesh (JIRA)" <ji...@apache.org> on 2017/07/20 17:53:05 UTC

[jira] [Updated] (EAGLE-771) AlertEngine: Make publishment kafka endpoint as optional

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

Jayesh updated EAGLE-771:
-------------------------
    Fix Version/s:     (was: v0.5.0)
                   v0.5.1

> AlertEngine: Make publishment kafka endpoint as optional
> --------------------------------------------------------
>
>                 Key: EAGLE-771
>                 URL: https://issues.apache.org/jira/browse/EAGLE-771
>             Project: Eagle
>          Issue Type: Bug
>    Affects Versions: v0.5.0
>            Reporter: Su Ralph
>            Assignee: Garrett Li
>             Fix For: v0.5.1
>
>
> For alert engine runtime, current kafka publishment have explicitly endpoint set, but in real deployment, these kafka endpoint are mostly the same the spout kafka url. 
> So we could make it as optional and by default reuse the kafka endpoint in the application.conf. This help reduce the redundancy of the metadata, and have a benefit that metadata would be the same for different deployment environments.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)