You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Olivér Szabó (JIRA)" <ji...@apache.org> on 2016/06/17 15:30:05 UTC
[jira] [Resolved] (AMBARI-17254) Log Search default log levels can
not be altered
[ https://issues.apache.org/jira/browse/AMBARI-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivér Szabó resolved AMBARI-17254.
-----------------------------------
Resolution: Fixed
committed to trunk:
{code:java}
commit 797a759a52f3da9838b1ee1bba5bf174c5aa0e63
Author: Miklos Gergely <mg...@hortonworks.com>
Date: Fri Jun 17 17:05:54 2016 +0200
AMBARI-17254. Log Search default log levels can not be altered (Miklos Gergely via oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit 21ed914a38dd562aa54bd7ff7b95f2036bbc8b09
Author: Miklos Gergely <mg...@hortonworks.com>
Date: Fri Jun 17 17:05:54 2016 +0200
AMBARI-17254. Log Search default log levels can not be altered (Miklos Gergely via oleewere)
{code}
> Log Search default log levels can not be altered
> ------------------------------------------------
>
> Key: AMBARI-17254
> URL: https://issues.apache.org/jira/browse/AMBARI-17254
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.4.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 2.4.0
>
>
> The default log levels (log levels to include) can not be altered, forever the ones set during the installation (more precisely: the one which is the value of the property during the first run of the portal) would be in effect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)