[
https://issues.apache.org/jira/browse/METRON-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167865#comment-16167865
]
ASF GitHub Bot commented on METRON-1188:
----------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/760
A bit on the second point: I would argue this is a new (more correct) take
if, for no other reason, that there isn't to my my knowledge other patterns to
emulate here (other projects don't let ambari have control over their zk
configs). The problem was letting ambari own the whole global config on disk
in the first place via the templating system. This moves to a more rational
approach of just having ambari apply patches to the config within the global
config that it owns, rather than controlling the whole file/global config.
> Ambari global configuration management broken
> ---------------------------------------------
>
> Key: METRON-1188
> URL: https://issues.apache.org/jira/browse/METRON-1188
> Project: Metron
> Issue Type: Bug
> Reporter: Michael Miklavcic
> Assignee: Michael Miklavcic
>
> Ambari currently ignores values from the UI when managing the global.json
> file. These values are hard-coded in the status_params.py file as part of the
> mpack. In addition, Ambari restarts are clobbering configuration changes in
> Zookeeper.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
