ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17616) Multiple fixes for Atlas integration in versions 0.1.0 and 0.7.0
Date Fri, 08 Jul 2016 19:39:10 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-17616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alejandro Fernandez updated AMBARI-17616:
-----------------------------------------
    Attachment:     (was: AMBARI-17616.branch-2.4.patch)

> 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
>
>
> 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)

Mime
View raw message