ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AMBARI-14026) Blueprints not setting correct defaults for HDFS proxyuser group settings
Date Tue, 24 Nov 2015 21:12:11 GMT


Hudson commented on AMBARI-14026:

FAILURE: Integrated in Ambari-branch-2.1 #932 (See [])
AMBARI-14026. Blueprints not setting correct defaults for HDFS proxyuser (rnettleton: [])
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/

> Blueprints not setting correct defaults for HDFS proxyuser group settings
> -------------------------------------------------------------------------
>                 Key: AMBARI-14026
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>            Priority: Critical
>             Fix For: 2.1.3
>         Attachments: AMBARI-14026.patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> The Ambari server handling of proxyuser settings has been updated in the UI's handling
of cluster configuration to use the "*" setting for the default group.
> Since the Blueprint configuration processor still handles configuration separately in
some respects, this default is now handled differently for the most part in Blueprints, as
the Blueprint processor will still set the default to be "users".  
> For example, the Blueprint processor currently sets the Hive-specific proxyuser group
property to:
> "hadoop.proxyuser.hive.groups" : "users",
> The Blueprint processor should be updated, such that the default is now "*" 
> for this property, and for all other service-specific proxyuser.*.groups properties in
> Since not all environments include the "users" group, the "*" group is a more valid default
value for this property.  This change will also bring the Blueprint processor more closely
in-line with the behavior of the UI, and so making the configuration more consistent across
both options. 
> I'm working on a fix for this, and will be submitting a patch shortly.  

This message was sent by Atlassian JIRA

View raw message