[
https://issues.apache.org/jira/browse/AMBARI-24916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692774#comment-16692774
]
Doroszlai, Attila commented on AMBARI-24916:
--------------------------------------------
Yes, the second one seems unnecessary:
https://github.com/apache/ambari/blob/93576b7c9bc25361ba1e43c9dfb08fc136667520/ambari-server/src/main/python/ambari_server/serverSetup.py#L1183-L1185
We can assume the return is intentional. You can setup several different JDBC
drivers to be used by services, and probably don't want to go over the regular
setup for each.
I think it would have been nice to if it had been added as a separate command
to avoid confusion, but at this point changing it would break existing
automation scripts.
> Ambari Server setup for non embedded DB miss out on default configuration
> -------------------------------------------------------------------------
>
> Key: AMBARI-24916
> URL: https://issues.apache.org/jira/browse/AMBARI-24916
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 3.0.0, 2.6.0, 2.6.1, 2.6.2, 2.7.0, 2.7.1, 2.7.2
> Reporter: Viraj Jasani
> Priority: Critical
> Fix For: 3.0.0, 2.6.0, 2.6.1, 2.6.2, 2.7.0, 2.7.1, 2.7.2
>
>
> If we setup Ambari Server with it's own embedded postgresql DB, we get all
> other configurations correctly e.g. setup command updates home.java,
> server.os_type, server.os_family etc in ambari.properties file that can be
> used during starting Ambari Server.
>
> However, if we provide server setup command with arguments to use
> non-embedded standalone DB, server setup does not update ambari.properties
> and does not perform any further setup utility that can be leveraged during
> starting Ambari Server.
> Example:
> 1) *ambari-server setup -j \{JDK_PATH} -s*
> This command updates ambari.properties for home.java, server.os_type,
> server.os_family etc.
>
> 2) *ambari-server setup --java-home=\{JDK_PATH} --jdbc-db=postgres
> --jdbc-driver=\{JDBC_DRIVER_PATH} --databasehost=\{IP_ADDR}
> --databaseport=5432 --databasename=ambari --postgresschema=ambari
> --databaseusername=\{DB_USER} --databasepassword=\{DB_PASSWD}
> --database=postgres -s*
> This command does not update ambari.properties and we need to update it
> manually to bring up Ambari Server. Hence, automation of server setup with
> server startup is blocked due to this bug.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
