[
https://issues.apache.org/jira/browse/METRON-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830066#comment-15830066
]
ASF GitHub Bot commented on METRON-503:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/316
Ok, my $0.02, for what it's worth, is that this is still very much needed.
Ambari is being considered for managing the configurations from a historical
manner and the proposal is that all config updates go through ambari's API (not
necessarily through the UI). This would mean that the Metron REST API, Stellar
REPL management functions (`CONFIG_PUT`) and Ambari itself would all send their
updates through the Ambari API before pushing to zookeeper.
All that being said, that is future state and not current state. We
shouldn't let the other good things here go uncommitted because we will
eventually use Ambari to be the backing persistent historical store for
configs. I think that I do agree with @merrimanr that given the discussion
about ambari rolling our own auditing config store doesn't make a lot of sense
and would just have to be ripped out later, so I'd be in favor of removing
those functions and capabilities from this PR.
> Metron REST API
> ---------------
>
> Key: METRON-503
> URL: https://issues.apache.org/jira/browse/METRON-503
> Project: Metron
> Issue Type: New Feature
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
> Attachments: Metron REST API.docx
>
>
> As discussed on the dev list ([DISCUSS] Metron REST API Requirements), this
> Jira includes adding a REST API to Metron.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
