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 BB46218EF2 for ; Thu, 2 Jul 2015 20:05:04 +0000 (UTC) Received: (qmail 1279 invoked by uid 500); 2 Jul 2015 20:05:04 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 1248 invoked by uid 500); 2 Jul 2015 20:05:04 -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 1237 invoked by uid 99); 2 Jul 2015 20:05:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2015 20:05:04 +0000 Date: Thu, 2 Jul 2015 20:05:04 +0000 (UTC) From: "Jaimin D Jetly (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-12265) Installer wizard: HBase tab shows 2 error count for empty configurations MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-12265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-12265: ------------------------------------ Description: With AMBARI-11069 commit, ambari-web did not displayed any site-properties.js configuration if API did not send that property's definition. Thus deleting a property in backend without deleting the same in site-properties for any particular stack largely became possible. There was a corner case that wasn't addressed by AMBARI-11069 commit which is related to a property that has multiple definition in different configuration file. Thus removing hbae.regionserver.global.memstore.upperLimit and hbae.regionserver.global.memstore.loweLimit from hbase-site of HDP-2.3 stack (which is present in hbase-site and ams-hbase-site) resulted into the property definition from site-property being honored instead of skipping it. This showed hbae.regionserver.global.memstore.upperLimit and hbae.regionserver.global.memstore.loweLimit on hbase config page with empty values invalidated with 2 error counts. > Installer wizard: HBase tab shows 2 error count for empty configurations > ------------------------------------------------------------------------ > > Key: AMBARI-12265 > URL: https://issues.apache.org/jira/browse/AMBARI-12265 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 2.1.0 > Reporter: Jaimin D Jetly > Assignee: Jaimin D Jetly > Priority: Critical > Fix For: 2.1.0 > > > With AMBARI-11069 commit, ambari-web did not displayed any site-properties.js configuration if API did not send that property's definition. > Thus deleting a property in backend without deleting the same in site-properties for any particular stack largely became possible. > There was a corner case that wasn't addressed by AMBARI-11069 commit which is related to a property that has multiple definition in different configuration file. > Thus removing hbae.regionserver.global.memstore.upperLimit and hbae.regionserver.global.memstore.loweLimit from hbase-site of HDP-2.3 stack (which is present in hbase-site and ams-hbase-site) resulted into the property definition from site-property being honored instead of skipping it. This showed hbae.regionserver.global.memstore.upperLimit and hbae.regionserver.global.memstore.loweLimit on hbase config page with empty values invalidated with 2 error counts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)