[jira] [Commented] (AMBARI-15919) Migrate instance specific data from one version to another.

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-15919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243769#comment-15243769 ] 

Hadoop QA commented on AMBARI-15919:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12798972/AMBARI-15919_trunk.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 4 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server ambari-views ambari-views/examples/calculator-view ambari-views/examples/cluster-view ambari-views/examples/favorite-view ambari-views/examples/hello-servlet-view ambari-views/examples/hello-spring-view ambari-views/examples/helloworld-view ambari-views/examples/phone-list-upgrade-view ambari-views/examples/phone-list-view ambari-views/examples/property-validator-view ambari-views/examples/property-view ambari-views/examples/restricted-view ambari-views/examples/simple-view ambari-views/examples/weather-view.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6482//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6482//console

This message is automatically generated.

> Migrate instance specific data from one version to another.
> -----------------------------------------------------------
>
>                 Key: AMBARI-15919
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15919
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.4.0
>            Reporter: Gaurav Nagar
>            Assignee: Gaurav Nagar
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15919_trunk.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)