You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/06/01 12:20:59 UTC

[jira] [Commented] (AMBARI-16836) View Instance: Data Migration

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

Hadoop QA commented on AMBARI-16836:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12807393/AMBARI-16836_branch-2.4-1.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:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:

                  org.apache.ambari.server.controller.internal.HostResourceProviderTest

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

This message is automatically generated.

> 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)