[
https://issues.apache.org/jira/browse/BIGTOP-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317742#comment-14317742
]
Evans Ye commented on BIGTOP-1662:
----------------------------------
{quote}it can be handed down from there as a default to all the sub-classes
(hdfs, yarn, mapred and httpfs).{quote}
Ok that's reasonable to me. These components won't adopt different realm at all.
{quote} All the realm-setting is already in place in cluster.yaml and should
work:{quote}
Sorry I'm not that familiar with hiera, but now I get it, it should work. I've
tested other components and the realm has been successfully propagated.
So, +1 on this patch, I'll commit this later.
> puppet: Fix hadoop configuration file incompleteness due to hiera conversion
> ----------------------------------------------------------------------------
>
> Key: BIGTOP-1662
> URL: https://issues.apache.org/jira/browse/BIGTOP-1662
> Project: Bigtop
> Issue Type: Bug
> Components: deployment
> Affects Versions: backlog
> Reporter: Michael Weiser
> Attachments:
> 0001-BIGTOP-1662-puppet-Fix-configuration-file-incomplete-2.patch,
> 0001-BIGTOP-1662-puppet-Fix-configuration-file-incomplete.patch
>
>
> The changes from BIGTOP-1634 omit kerberos_realm and
> hadoop_security_authentication variables from some classes so that they're
> not correctly entered in the generated configuration files. Also, a hasty
> "fix" to hadoop-env.sh causes all variables to remain unset always.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
