You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Babiichuk (JIRA)" <ji...@apache.org> on 2015/10/06 15:31:28 UTC
[jira] [Updated] (AMBARI-13323) JDBC connection string for Ranger
does not update when changing database option
[ https://issues.apache.org/jira/browse/AMBARI-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrii Babiichuk updated AMBARI-13323:
--------------------------------------
Attachment: AMBARI-13323.patch
> JDBC connection string for Ranger does not update when changing database option
> -------------------------------------------------------------------------------
>
> Key: AMBARI-13323
> URL: https://issues.apache.org/jira/browse/AMBARI-13323
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.3
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13323.patch
>
>
> STR:
> Go to Ranger smart config page and open Ranger Admin Tab
> Change Ranger DB name from ranger to ranger1. This will update JDBC connection string to jdbc:mysql://c6401.ambari.apache.org/ranger1 as expected
> Now Change DB FLAVOR from MySQL to POSTGRES.
> Expected Result: JDBC connection string should be updated to jdbc:postgresql://c6401.ambari.apache.org:5432/ranger1
> Actual Result: JDBC connection string remains jdbc:mysql://c6401.ambari.apache.org/ranger1
> It was noticed that recommendation API is returning the expected result but UI is not updating it.
> The STR above reproduces the issue often. In case if it does not reproduce on the first trial, please try the STR more than once.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)