[
https://issues.apache.org/jira/browse/AMBARI-16995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863082#comment-15863082
]
Aravindan Vijayan commented on AMBARI-16995:
--------------------------------------------
Closing this "as designed" for the following reasons ...
1. The main issue here is that the 3 Atlas configurations are not auto
populated which forces user input. That is as designed as described above.
2. The use of the param.py variables (i.e. hbase_zookeeper_quorum) has been
resolved as part of AMBARI-17098.
3. The atlas.graph.index.search.solr.zookeeper-url property dependency to
LogSearch is probably not a good idea since the property is only conditionally
dependent on LogSearch.
> While installing cluster from UI, 3 atlas fields are not auto populated in
> customize services page
> --------------------------------------------------------------------------------------------------
>
> Key: AMBARI-16995
> URL: https://issues.apache.org/jira/browse/AMBARI-16995
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Environment: ambari-server version: ambari-server-2.4.0.0-622.x86_64
> ambari-server --hash: dc340e8c6cb4fa6c062f805cc1917f62299a5f50
> HDP Stack: 2.5
> HDP Version: 2.5.0.0-614
> Ambari DB: :Oracle
> Reporter: Vivek Rathod
> Priority: Critical
> Fix For: 2.5.0
>
>
> Here are those properties:
> atlas.audit.hbase.zookeeper.quorum
> atlas.graph.index.search.solr.zookeeper-url
> atlas.graph.storage.hostname
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
