Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A8239200C3A for ; Fri, 3 Mar 2017 02:28:52 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A6CF8160B7A; Fri, 3 Mar 2017 01:28:52 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id F1B40160B6F for ; Fri, 3 Mar 2017 02:28:51 +0100 (CET) Received: (qmail 3959 invoked by uid 500); 3 Mar 2017 01:28:51 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 3950 invoked by uid 99); 3 Mar 2017 01:28:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Mar 2017 01:28:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id C64271A002A for ; Fri, 3 Mar 2017 01:28:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.547 X-Spam-Level: X-Spam-Status: No, score=-1.547 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id pZi9XogF2EuG for ; Fri, 3 Mar 2017 01:28:50 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 0089A5FD84 for ; Fri, 3 Mar 2017 01:28:50 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 2EA5BE08C3 for ; Fri, 3 Mar 2017 01:28:46 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A4ADF2416A for ; Fri, 3 Mar 2017 01:28:45 +0000 (UTC) Date: Fri, 3 Mar 2017 01:28:45 +0000 (UTC) From: "Hudson (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-20257) Log Search upgrade to 2.5 should handle renamed properties safely MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 03 Mar 2017 01:28:52 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893535#comment-15893535 ] Hudson commented on AMBARI-20257: --------------------------------- SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6923 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6923/]) 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=7e2eb293def46ee172c05471bc7fc6954eafd98b]) * (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)