[
https://issues.apache.org/jira/browse/AMBARI-21067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019561#comment-16019561
]
Hudson commented on AMBARI-21067:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7513 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7513/])
AMBARI-21067. Atlas config values not getting populated on BP cluster
(smagyari:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=74972de559b21633288c03785dc672e792a172bb])
* (edit)
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml
> Atlas config values not getting populated on BP cluster install with strategy
> : "NEVER_APPLY"
> ---------------------------------------------------------------------------------------------
>
> Key: AMBARI-21067
> URL: https://issues.apache.org/jira/browse/AMBARI-21067
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Sandor Magyari
> Assignee: Sandor Magyari
> Priority: Critical
> Fix For: 3.0.0, 2.5.2
>
> Attachments: AMBARI-21067.patch
>
>
> After cluster install, the following 5 ATLAS's 'application-properties'
> configs are empty:
> {code}
> atlas.graph.index.search.solr.zookeeper-url
> atlas.graph.storage.hostname
> atlas.kafka.bootstrap.servers
> atlas.kafka.zookeeper.connect
> atlas.audit.hbase.zookeeper.quorum
> {code}
> BlueprintConfigProcessor should configure these properties in case there's no
> stack advisor strategy set.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
