[
https://issues.apache.org/jira/browse/AMBARI-17616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367266#comment-15367266
]
Hadoop QA commented on AMBARI-17616:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816752/AMBARI-17616.trunk.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7733//console
This message is automatically generated.
> Multiple fixes for Atlas integration in versions 0.1.0 and 0.7.0
> ----------------------------------------------------------------
>
> Key: AMBARI-17616
> URL: https://issues.apache.org/jira/browse/AMBARI-17616
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.4.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17616.branch-2.4.patch, AMBARI-17616.trunk.patch
>
>
> This Jira contains several fixes.
> 1. Separate Atlas versions 0.1.0 (HDP 2.3 and 2.4), and 0.7.0 (HDP 2.5) for
> Atlas.
> This way, all of the LDAP/AD changes only affect HDP 2.5.
> This means that HDP 2.5 will have the smart configs theme.
> 2. Allow atlas.authentication.method.ldap.type to contain the value "none"
> If the value is none, then do not require any of the LDAP or AD configs.
> Stack advisor must support this change.
> 3. For the LDAP and AD configs that are required, do not allow an empty
> value. Only these 4 LDAP/AD properties can be optional:
> atlas.authentication.method.ldap.referral
> atlas.authentication.method.ldap.default.role
> atlas.authentication.method.ldap.ad.referral
> atlas.authentication.method.ldap.ad.default.role
> 4. Set all of the configs in atlas-application.properties to have,
> {code}
> <on-ambari-upgrade add="false"/>
> {code}
> 5. When generating the file atlas-application.properties.xml for Hive,
> Falcon, Storm, and Sqoop, only copy a subset of the configs from Atlas'
> application.properties, these configs are
> {code}
> "atlas.kafka.zookeeper.connect",
> "atlas.kafka.bootstrap.servers",
> "atlas.kafka.zookeeper.session.timeout.ms",
> "atlas.kafka.zookeeper.connection.timeout.ms",
> "atlas.kafka.zookeeper.sync.time.ms",
> "atlas.kafka.hook.group.id",
> "atlas.notification.create.topics",
> "atlas.notification.replicas",
> "atlas.notification.topics",
> "atlas.notification.kafka.service.principal",
> "atlas.notification.kafka.keytab.location",
> "atlas.jaas.KafkaClient.loginModuleName",
> "atlas.jaas.KafkaClient.loginModuleControlFlag",
> "atlas.jaas.KafkaClient.option.useKeyTab",
> "atlas.jaas.KafkaClient.option.storeKey",
> "atlas.jaas.KafkaClient.option.serviceName",
> "atlas.jaas.KafkaClient.option.keyTab",
> "atlas.jaas.KafkaClient.option.principal",
> "atlas.cluster.name"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
