Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8D61B186F4 for ; Mon, 28 Sep 2015 17:49:06 +0000 (UTC) Received: (qmail 98835 invoked by uid 500); 28 Sep 2015 17:49:05 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 98796 invoked by uid 500); 28 Sep 2015 17:49:05 -0000 Mailing-List: contact dev-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 dev@ambari.apache.org Received: (qmail 98765 invoked by uid 99); 28 Sep 2015 17:49:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Sep 2015 17:49:04 +0000 Date: Mon, 28 Sep 2015 17:49:04 +0000 (UTC) From: "Nahappan Somasundaram (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-13261) Modify repository version resource handler update RESTful API to update metaInfo table as well MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Nahappan Somasundaram created AMBARI-13261: ---------------------------------------------- Summary: Modify repository version resource handler update RESTful API to update metaInfo table as well Key: AMBARI-13261 URL: https://issues.apache.org/jira/browse/AMBARI-13261 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.2.0 Reporter: Nahappan Somasundaram Assignee: Nahappan Somasundaram Fix For: 2.2.0 As we transition from metaInfo table to repo_version table, updating repo_version table must update metaInfo table so that scenarios that read from metaInfo table get the correct URLs. This will also help with fixing BUG-40202 - Disable old APIs to manage baseurl values. During cluster setup, the UI uses the old API to write to metaInfo table. During services installation, this information gets replicated to repo_version table. The UI will be modified to use the new API (repo_version table API) to store the URLs. However, for backward compatibility, we need this information in metaInfo table as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)