[AMBARI-15919] Migrate instance specific data from one version to another.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.4.0
• Component/s: ambari-views
• Assignee: Gaurav Nagar
• Reporter: Gaurav Nagar
• Created: 15/Apr/16 14:19
• Updated: 26/Apr/16 12:35
• Resolved: 26/Apr/16 06:56

Description

It is critical that we provide a way to migrate instance data and view data information between versions of views. We need to support the following use case:

• New version of view is instantiated. Since instance specific data will not be available to the new instance of the view (if the version has changed), there needs to be a way of migrating existing information over to the new view instance.
• The Ambari view framework needs to provide a facility to invoke call back handlers (of sorts) to allow the view itself to handle the migration from and older version to the current version.

An example...

After a view instance (X1) is created (say from XView 1.0.0), a view might use instance data and/or datastore data. When a new view is released (say from XView 2.0.0), an ambari admin will want to create a new instance (X2) and migrate the data from the existing instance (X1). Ambari should provide a mechanism to perform this migration.

1) The ambari admin creates new instance X2 in the admin interface.
2) The ambari admin can select to migrate data from an existing instance.
3) The ambari admin initiates the migration of instance and datastore. The ambari views framework starts the processing of instance + datastore data movement (copying) to the new X2 instance scope.
4) The framework should call into a hook in the view in case any changes are needed to the X1 info before they saved in the new X2 instance.

Issue Links

• links to: Apache Review Link