[
https://issues.apache.org/jira/browse/AMBARI-16836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DIPAYAN BHOWMICK updated AMBARI-16836:
--------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
AMBARI-16836 : View Instance: Data Migration
> View Instance: Data Migration
> -----------------------------
>
> Key: AMBARI-16836
> URL: https://issues.apache.org/jira/browse/AMBARI-16836
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.4.0
> Reporter: Nitiraj Singh Rathore
> Assignee: Nitiraj Singh Rathore
> Fix For: 2.4.0
>
> Attachments: AMBARI-16836_branch-2.4-1.patch
>
>
> Provide instructions for performing the following:
> 1) TWO INSTANCES, SAME VERSION
> User has view100 instance A. Create view100 instance B. After creation of
> instance B, how the Admin will migrate data (entity, instance, perms) from A
> -> B
> 2) TWO INSTANCES, NEWER VERSION
> User has view100 instance A. Create view200 instance B. After creation of
> instance B, how the Admin will migrate data (entity, instance, perms) from A
> -> B.
> 3) NEWER VERSION IN NEW AMBARI
> User has view100 instance A in Ambari 2.2.2. They upgrade to Ambari 2.4.0
> with a newer version of view200. The view200 instance is not auto-created. So
> would they just follow #2?
> 4) NEW INSTANCE -> NEWER VERSION
> User has view100 instance A and when they create view200 instance B,
> automatically migrate data (entity, instance, perms) from A -> B.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
