ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-9476) Use JDBC driver symbolic link instead of filename in ranger install
Date Fri, 06 Feb 2015 23:40:35 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yusaku Sako resolved AMBARI-9476.
---------------------------------
    Resolution: Fixed

Committed to trunk.

> Use JDBC driver symbolic link instead of filename in ranger install
> -------------------------------------------------------------------
>
>                 Key: AMBARI-9476
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9476
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Velmurugan Periasamy
>            Assignee: Velmurugan Periasamy
>             Fix For: 2.0.0
>
>
> One of the requirements for adding Ranger to an existing cluster is to run "ambari-server
setup" to deploy the JDBC driver.
> Below command is run to meet this requirement.
> {code}
> ambari-server setup --jdbc-db=mysql --jdbc-driver=/usr/share/java/mysql-connector-java-5.1.17.jar
> {code}
> However, this caused Ranger install phase to fail, because it is trying to download the
driver file from http://ambari-host:8080/resources/mysql-connector-java.jar, which does not
exist.
> Note that if you had run the below it works.
> {code}
> ambari-server setup --jdbc-db=mysql --jdbc-driver=/usr/share/java/mysql-connector-java.jar
> {code}
> However, relying on the exact filename is error prone.
> The ambari-server setup command creates a symlink called "mysql-jdbc-driver.jar" that
points to the actual jar file.  So the ranger setup script should use that name instead for
MySQL.  Also check corresponding driver name for Oracle.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message