You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Su Ralph (JIRA)" <ji...@apache.org> on 2016/11/15 09:18:58 UTC
[jira] [Created] (EAGLE-771) AlertEngine: Make publishment kafka
endpoint as optional
Su Ralph created EAGLE-771:
------------------------------
Summary: 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: Su Ralph
Fix For: v0.5.0
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.3.4#6332)