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 B3E9C200B67 for ; Tue, 12 Jul 2016 01:21:12 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B0CDF160A78; Mon, 11 Jul 2016 23:21:12 +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 0D343160A7D for ; Tue, 12 Jul 2016 01:21:11 +0200 (CEST) Received: (qmail 72998 invoked by uid 500); 11 Jul 2016 23:21:11 -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 72928 invoked by uid 99); 11 Jul 2016 23:21:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jul 2016 23:21:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 106242C02AA for ; Mon, 11 Jul 2016 23:21:11 +0000 (UTC) Date: Mon, 11 Jul 2016 23:21:11 +0000 (UTC) From: "Jayush Luniya (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 11 Jul 2016 23:21:12 -0000 [ https://issues.apache.org/jira/browse/AMBARI-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-17285: ----------------------------------- Priority: Critical (was: Major) > Custom service repos in repoinfo.xml got overwritten by public VDFs > ------------------------------------------------------------------- > > Key: AMBARI-17285 > URL: https://issues.apache.org/jira/browse/AMBARI-17285 > Project: Ambari > Issue Type: Bug > Reporter: Alexander Denissov > Priority: Critical > Fix For: 2.4.0 > > > Ambari 2.4 introduced Version Definition Files that break the functionality of adding a custom service repo, since custom services do not have an entry in the public VDF. > In the case of HAWQ, the plugin is installed on Ambari host and it adds the new repo information to the repoinfo.xml of all available stacks on the file system. Once Ambari cluster creation wizard queries the latest repo info from the public URLs, it will get the info for all stack repos, but not the custom ones. > So, the logic should be: > 1. Use default repoinfo (from file system) as the base > 2. Query public VDF, if available > 3. For each entry in public VDF overwrite values in the default repoinfo > 4. Entries in default repoinfo that do not have corresponding entries in VDF should stay intact > This way custom services can be added via file edit and the latest information can still be retrieved and applied for the standard stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)