[
https://issues.apache.org/jira/browse/AMBARI-11563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566339#comment-14566339
]
Hudson commented on AMBARI-11563:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2761 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2761/])
AMBARI-11563. Blueprints does not filter out conditional properties from
cluster configuration. (rnettleton) (rnettleton:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=517bdeb4a91736f7b1a05318bfd45678e9171f3c)
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/Stack.java
> Blueprints does not filter out conditional properties from cluster
> configuration
> --------------------------------------------------------------------------------
>
> Key: AMBARI-11563
> URL: https://issues.apache.org/jira/browse/AMBARI-11563
> 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.0
>
> Attachments: AMBARI-11563.patch
>
>
> The Blueprints processor currently has no notion of "optional" properties in
> a cluster's configuration. The Blueprints processor uses the stack
> definitions to determine the set of properties to include and extend in the
> process of deploying a cluster.
> There are some properties in HBase and Hive that are "conditional" in nature.
> An example of this is the "hbase.coprocessor.regionserver.classes" config
> property in "hbase-site". This property should only be set when HBase
> authorization is configured to be enabled.
> Currently, a Blueprints deployment of HBase will set this property to the
> default, empty value, and this will be included in the Cluster configuration.
> This causes problems after the cluster deployment completes, since the
> Ambari UI will display this property as required, even through authorization
> is not configured to be enabled in this cluster.
> The Blueprints configuration processor needs to be modified to exclude any
> properties that don't meet certain conditions:
> 1. HBase Authorization (on/off)
> 2. Hive Authentication (on/off)
> 3. HDFS NameNode properties that are only useful in a non-HA scenario must be
> filtered out in an HDFS NameNode HA deployment.
> I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
