[jira] [Commented] (AMBARI-12822) Implement SQL Anywhere as a supported DB for Ambari

["Jean-Baptiste Musso (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-12822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694511#comment-16694511 ] 

Jean-Baptiste Musso commented on AMBARI-12822:
----------------------------------------------

For further reference, would you please share info on why the "jdbc_hostname" value is automatically set to the host's FQDN when "database_host" is set to "localhost"?

See: https://github.com/apache/ambari/blob/ae3d9aa3abfa589a568a77e4c7cf0c7656bdfc65/ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py#L296

This behavior is not entirely clear to us and causes connection issues to PostgreSQL on dev/test environment where it makes sense for us to have Ambari server connect to a PostgreSQL instance running on the same host via localhost / local loop.

Depending on the rationale behind this behavior, this comment could be root for spawning a distinct issue in JIRA.

Thanks,

(Linking to Github -- I'm currently getting 404 errors on https://git-wip-us.apache.org/repos/asf?p=ambari.git)

> Implement SQL Anywhere as a supported DB for Ambari
> ---------------------------------------------------
>
>                 Key: AMBARI-12822
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12822
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.2
>            Reporter: Myroslav Papirkovskyi
>            Assignee: Myroslav Papirkovskyi
>            Priority: Critical
>             Fix For: 2.1.2
>
>
> Ambari must support SQLA as the back-end RDBMS to store meta-data information



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)