[
https://issues.apache.org/jira/browse/AMBARI-15894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-15894:
---------------------------------------
Status: Patch Available (was: Open)
> After adding support for real jdbc jar names, verify the post Ambari upgrade
> nothing breaks
> -------------------------------------------------------------------------------------------
>
> Key: AMBARI-15894
> URL: https://issues.apache.org/jira/browse/AMBARI-15894
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15894.patch
>
>
> Lets think through the upgrade scenario again:
> Prior to upgrade we know of hard-coded names and the system is in working
> state
> During upgrade, lets pre-populate the ambari.properties file with the old
> hard-coded values (think of them as the real names as thats what we know)
> If user wants to use real name, they can call ambari-server setup ...
> Net goal is to not have user do anything post Ambari upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
