ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Miklos Gergely (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20578) Log Search Configuration API
Date Wed, 12 Apr 2017 13:03:41 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-20578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965789#comment-15965789
] 

Miklos Gergely commented on AMBARI-20578:
-----------------------------------------

committed to trunk:
{code:java}
commit 0ac0ba424e31db38704d8e7a59ac60b853094cda
Author: Miklos Gergely <mgergely@hortonworks.com>
Date:   Wed Apr 12 15:02:14 2017 +0200

    AMBARI-20578 Log Search Configuration API (mgergely)
    
    Change-Id: I2415e9402fa002dedb566cfebada4cf34ef1d4a6
{code}


> 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)

Mime
View raw message