[
https://issues.apache.org/jira/browse/AMBARI-19001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705238#comment-15705238
]
Hadoop QA commented on AMBARI-19001:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840680/AMBARI-19001.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 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9427//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9427//console
This message is automatically generated.
> Support configurable grok filters (output + ambari)
> ---------------------------------------------------
>
> Key: AMBARI-19001
> URL: https://issues.apache.org/jira/browse/AMBARI-19001
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, ambari-server
> Affects Versions: 2.4.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19001.patch
>
>
> Support configurable output and ambari grok filter configs from ambari.
> Ambari log patterns can change, so its a good idea to make it editable.
> Also with a configurable output, we can extend the logfeeder output to use
> e.g. kafka
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
