[ 
https://issues.apache.org/jira/browse/AMBARI-20257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893397#comment-15893397
 ] 

Miklos Gergely commented on AMBARI-20257:
-----------------------------------------

committed to trunk:
{code:java}
commit 7e2eb293def46ee172c05471bc7fc6954eafd98b
Author: Miklos Gergely <[email protected]>
Date:   Fri Mar 3 01:38:11 2017 +0100

    AMBARI-20257 Log Search upgrade to 2.5 should handle renamed properties 
safely (mgergely)
    
    Change-Id: I162e210a02e9c56575f682cb6d65074c18efd8b9
{code}

committed to branch-2.5:
{code:java}
commit de227f6d1f99212bfd131af6ce44dff6c2ce59b6
Author: Miklos Gergely <[email protected]>
Date:   Fri Mar 3 01:39:28 2017 +0100

    AMBARI-20257 Log Search upgrade to 2.5 should handle renamed properties 
safely (mgergely)
    
    Change-Id: I35385a0bf3d596bea864767a04ea8d930404e7de
{code}

> 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)

Reply via email to