[ https://issues.apache.org/jira/browse/AMBARI-20257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893528#comment-15893528 ]
Hudson commented on AMBARI-20257: --------------------------------- SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1162 (See [https://builds.apache.org/job/Ambari-branch-2.5/1162/]) AMBARI-20257 Log Search upgrade to 2.5 should handle renamed properties (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=de227f6d1f99212bfd131af6ce44dff6c2ce59b6]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-properties.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java > 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)