[
https://issues.apache.org/jira/browse/AMBARI-24916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778271#comment-16778271
]
Hudson commented on AMBARI-24916:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10471 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10471/])
AMBARI-24916. Add setup-jdbc command (#2634) (vishalsuvagia:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=7e94d625fe019a2966e0b62a76d3c2cb4402e7fa])
* (edit) ambari-server/src/main/python/ambari-server.py
* (edit) ambari-server/src/main/python/ambari_server/setupActions.py
* (edit) ambari-server/src/test/python/TestAmbariServer.py
* (edit) ambari-server/src/main/python/ambari_server/serverSetup.py
* (edit) ambari-server/sbin/ambari-server
> 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
> Assignee: Doroszlai, Attila
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)
