[
https://issues.apache.org/jira/browse/AMBARI-12265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613713#comment-14613713
]
Hudson commented on AMBARI-12265:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.1 #165 (See
[https://builds.apache.org/job/Ambari-branch-2.1/165/])
AMBARI-12265. Installer wizard: HBase tab shows 2 error count for empty
configurations. (jaimin) (jaimin:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c245df22d371c43e7e574a62c1214bbb87bc11e9)
* ambari-web/app/utils/config.js
> 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
>
> Attachments: AMBARI-12265.patch
>
>
> 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)
