[
https://issues.apache.org/jira/browse/AMBARI-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945291#comment-14945291
]
Hudson commented on AMBARI-13323:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.1 #643 (See
[https://builds.apache.org/job/Ambari-branch-2.1/643/])
AMBARI-13323 JDBC connection string for Ranger does not update when
(ababiichuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=00aabde5e2b3e91060e08b483374bd6828937953])
* ambari-web/app/views/common/controls_view.js
> 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)
