[
https://issues.apache.org/jira/browse/AMBARI-20257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890571#comment-15890571
]
Hadoop QA commented on AMBARI-20257:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12855387/AMBARI-20257.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/10828//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10828//console
This message is automatically generated.
> Log Search upgrade to 2.5 should handle renamed properties safely
> -----------------------------------------------------------------
>
> Key: AMBARI-20257
> URL: https://issues.apache.org/jira/browse/AMBARI-20257
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.5.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-20257.patch
>
>
> Log Search upgrade to 2.5 renames some variables. If for some reason the
> upgrade is repeated, it tries to rename them again, which causes some
> problem, as the original variables are not present anymore.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
