[
https://issues.apache.org/jira/browse/AMBARI-20578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966924#comment-15966924
]
Hudson commented on AMBARI-20578:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7283 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7283/])
AMBARI-20578 APPENDUM-2 Log Search Configuration API (mgergely) (mgergely:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=aca12b7a3387211a51718026215a30877960035d])
* (edit)
ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/params.py
> Log Search Configuration API
> ----------------------------
>
> Key: AMBARI-20578
> URL: https://issues.apache.org/jira/browse/AMBARI-20578
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 3.0.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 3.0.0
>
>
> Log Search should store it's configurations (inputs, filters) by using an
> API, which the user may implement as well to use their own way of storing the
> configurations. By default for now we offer to store everything in ZooKeeper.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
