ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "bhuvnesh chaudhary (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15254) Ambari config update does not handle removals properly
Date Thu, 03 Mar 2016 20:04:18 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178514#comment-15178514
] 

bhuvnesh chaudhary commented on AMBARI-15254:
---------------------------------------------

Committed to branch-2.2
commit 91b224e0f8f3956fd4c7bb08ef21999ec044b7a3


> Ambari config update does not handle removals properly
> ------------------------------------------------------
>
>                 Key: AMBARI-15254
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15254
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk, 2.2.0
>            Reporter: Lav Jain
>            Assignee: Lav Jain
>             Fix For: 2.3.0, 2.2.2
>
>         Attachments: AMBARI-15254.branch22.patch, AMBARI-15254.patch
>
>
> ConfigHelper.updateConfigType takes in config_type (e.g. hdfs-site), map of updates (key
value pairs) and a list of removals (properties).
> The current implementation is skipping the updates to configuration if the Map of updates
is empty, even if there are properties to be removed.
> This is causing problem during disabling of kerberos for some components (like HAWQ)
because some config parameters that are present in kerberos.json must be removed.



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

Mime
View raw message