You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hari Sekhon (JIRA)" <ji...@apache.org> on 2018/07/24 10:00:02 UTC
[jira] [Updated] (AMBARI-24345) Database Type Migration Support &
Documentation (eg. PostreSQL => MySQL, MYSQL => PostgreSQL)
[ https://issues.apache.org/jira/browse/AMBARI-24345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Sekhon updated AMBARI-24345:
---------------------------------
Summary: Database Type Migration Support & Documentation (eg. PostreSQL => MySQL, MYSQL => PostgreSQL) (was: Database Type Migration Support & Documentation (PostreSQL => MySQL or MYSQL => PostgreSQL))
> Database Type Migration Support & Documentation (eg. PostreSQL => MySQL, MYSQL => PostgreSQL)
> ---------------------------------------------------------------------------------------------
>
> Key: AMBARI-24345
> URL: https://issues.apache.org/jira/browse/AMBARI-24345
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, documentation
> Affects Versions: 2.6.0
> Reporter: Hari Sekhon
> Priority: Major
>
> Improvement Request to official support and document migrating from one Ambari DB type to another (eg. migrating from PostgreSQL to MySQL or vice versa).
> A colleague in Hortonworks suggests that there are schema differences that prevent backup and restore to other database type and I cannot see good documentation on doing this, leaving using to have to do an Ambari takeover operation, and lose config change history.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)