[
https://issues.apache.org/jira/browse/AMBARI-18161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428124#comment-15428124
]
Hadoop QA commented on AMBARI-18161:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824531/AMBARI-18161.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8461//console
This message is automatically generated.
> Support UNKNOWN log level for Log Search
> ----------------------------------------
>
> Key: AMBARI-18161
> URL: https://issues.apache.org/jira/browse/AMBARI-18161
> Project: Ambari
> Issue Type: Improvement
> Components: logsearch
> Affects Versions: 2.4.0
> Reporter: Dharmesh Makwana
> Assignee: Dharmesh Makwana
> Fix For: 2.5.0
>
> Attachments: AMBARI-18161.patch
>
>
> In some cases, there are no log level inforamtion in logs, therefore we need
> to map the log to a log level, but that is maybe not the proper solution
> (e.g. we are mapping X log to INFO log level, but maybe a customer wants to
> see only error,warn,fatal level logs, because customer has too many INFO
> level logs..in that case logs only visible if INFO level filter is on)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
