You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Gautam Borad (JIRA)" <ji...@apache.org> on 2015/11/24 12:21:10 UTC
[jira] [Updated] (AMBARI-14033) Wrong Audit JDBC URL generated,
even though JDBC URL format is overridden by user
[ https://issues.apache.org/jira/browse/AMBARI-14033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gautam Borad updated AMBARI-14033:
----------------------------------
Description:
*Steps to reproduce:*
-- Install Ranger with Oracle 12C
-- Use SID format for DB host (host:port:SID) e.g. hostname:1521:ORCL
-- Override connect string (jdbc:oracle:thin:@hostname:1521:ORCL - note that there is no //, which was generated by Ambari, but should be removed to get it to work)
-- Complete the install
-- Ranger will work fine, but DB auditing will not work
*Root Cause*
When JDBC string is overridden, ranger-admin-site.xml->ranger.jpa.jdbc.url is properly generated.
But, {{ranger-admin-site.xml->ranger.jpa.audit.jdbc.url}} and {{ranger-<component>\-audit.xml\->xasecure.audit.destination.db.jdbc.url}} are generated wrong. They both refer to {{audit_jdbc_url}} macro, which is apparently calculated incorrectly.
*Workaround*
Manually override ranger.jpa.audit.jdbc.url and xasecure.audit.destination.db.jdbc.url
*Actual solution*
Calculate the variable properly, so that user does not have to enter it again.
was:
*Steps to reproduce:*
-- Install Ranger with Oracle 12C
-- Use SID format for DB host (host:port:SID) e.g. hostname:1521:ORCL
-- Override connect string (jdbc:oracle:thin:@hostname:1521:ORCL - note that there is no //, which was generated by Ambari, but should be removed to get it to work)
-- Complete the install
-- Ranger will work fine, but DB auditing will not work
*Root Cause*
When JDBC string is overridden, ranger-admin-site.xml->ranger.jpa.jdbc.url is property generated.
But, {{ranger-admin-site.xml->ranger.jpa.audit.jdbc.url}} and {{ranger-<component>\-audit.xml\->xasecure.audit.destination.db.jdbc.url}} are generated wrong. They both refer to {{audit_jdbc_url}} macro, which is apparently calculated incorrectly.
*Workaround*
Manually override ranger.jpa.audit.jdbc.url and xasecure.audit.destination.db.jdbc.url
*Actual solution*
Calculate the variable properly, so that user does not have to enter it again.
> Wrong Audit JDBC URL generated, even though JDBC URL format is overridden by user
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-14033
> URL: https://issues.apache.org/jira/browse/AMBARI-14033
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.3
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Fix For: 2.2.0, 2.1.3
>
>
> *Steps to reproduce:*
> -- Install Ranger with Oracle 12C
> -- Use SID format for DB host (host:port:SID) e.g. hostname:1521:ORCL
> -- Override connect string (jdbc:oracle:thin:@hostname:1521:ORCL - note that there is no //, which was generated by Ambari, but should be removed to get it to work)
> -- Complete the install
> -- Ranger will work fine, but DB auditing will not work
> *Root Cause*
> When JDBC string is overridden, ranger-admin-site.xml->ranger.jpa.jdbc.url is properly generated.
> But, {{ranger-admin-site.xml->ranger.jpa.audit.jdbc.url}} and {{ranger-<component>\-audit.xml\->xasecure.audit.destination.db.jdbc.url}} are generated wrong. They both refer to {{audit_jdbc_url}} macro, which is apparently calculated incorrectly.
> *Workaround*
> Manually override ranger.jpa.audit.jdbc.url and xasecure.audit.destination.db.jdbc.url
> *Actual solution*
> Calculate the variable properly, so that user does not have to enter it again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)