[jira] [Updated] (AMBARI-12010) Enabling and disabling Phoenix in HBase configs leaves certain configs changed

["Srimanth Gunturi (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-12010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Srimanth Gunturi updated AMBARI-12010:
--------------------------------------
    Attachment: AMBARI-12010.patch

The problem is that when installing cluster, we are not removing configs that should have been marked as deleted. Since we are not doing it, we start off in an inconsistent state. Enabling and disabling Phoenix configs correctly changes values, but the initial inconsistent state bleeds through and shows as more configs were changed even when not.

The fix is to apply changes even on the first /recommendation call in installer.

> Enabling and disabling Phoenix in HBase configs leaves certain configs changed
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-12010
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12010
>             Project: Ambari
>          Issue Type: Bug
>          Components: contrib
>    Affects Versions: 2.1.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12010.patch
>
>
> # Deployed cluster with HBase
> # Went on HBase Settings tab
> # Changed 'Enable Phoenix' property to Enabled
> # Popup near Save/Discard tab says 'There are 4 configuration changes in 1 service'
> # Get 'Enable Phoenix' property back to Disabled
> # Popup says 'There are 3 configuration changes in 1 service' and Save/Discard buttons are still available.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)