metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cestella <...@git.apache.org>
Subject [GitHub] incubator-metron issue #316: METRON-503: Metron REST API
Date Thu, 19 Jan 2017 14:58:35 GMT
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.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message