[
https://issues.apache.org/jira/browse/AMBARI-21623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110290#comment-16110290
]
Hadoop QA commented on AMBARI-21623:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12879847/AMBARI-21623.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-config-api
ambari-logsearch/ambari-logsearch-config-zookeeper
ambari-logsearch/ambari-logsearch-logfeeder
ambari-logsearch/ambari-logsearch-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11910//console
This message is automatically generated.
> Log Search Config should be separated into a Server and Log Feeder interface
> ----------------------------------------------------------------------------
>
> Key: AMBARI-21623
> URL: https://issues.apache.org/jira/browse/AMBARI-21623
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch
> Affects Versions: 3.0.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 3.0.0
>
> Attachments: AMBARI-21623.patch
>
>
> Log Search Config is getting too complex, it serves too many kind of things.
> It should be separated into two interfaces, one for the Server and one for
> the Log Feeders to make it cleaner.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
