[
https://issues.apache.org/jira/browse/AMBARI-18616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15584316#comment-15584316
]
Hadoop QA commented on AMBARI-18616:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12833829/AMBARI-18616.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8897//console
This message is automatically generated.
> Fix Log Search User Config bug
> ------------------------------
>
> Key: AMBARI-18616
> URL: https://issues.apache.org/jira/browse/AMBARI-18616
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.4.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-18616.patch
>
>
> Log Search User Config UI screen does not offer the chance to modify the
> filter settings for those logs which don't have any log entries loaded so
> far. For these logs the initial settings will be in effect until the first
> modification of the filters when all of these settings will be erased, and
> thus every log will be loaded for them without filtering.
> The User Config UI should always show all the logs, first those which already
> have some log entries in the solr, then the rest.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
