From dev-return-21282-archive-asf-public=cust-asf.ponee.io@atlas.apache.org Fri Feb 23 23:01:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 272BB180652 for ; Fri, 23 Feb 2018 23:01:04 +0100 (CET) Received: (qmail 90095 invoked by uid 500); 23 Feb 2018 22:01:04 -0000 Mailing-List: contact dev-help@atlas.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@atlas.apache.org Delivered-To: mailing list dev@atlas.apache.org Received: (qmail 90084 invoked by uid 99); 23 Feb 2018 22:01:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Feb 2018 22:01:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A9D0918038B for ; Fri, 23 Feb 2018 22:01:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id NRygK3nyYqvU for ; Fri, 23 Feb 2018 22:01:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id EC6805FAE2 for ; Fri, 23 Feb 2018 22:01:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6BC13E091C for ; Fri, 23 Feb 2018 22:01:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 8587921909 for ; Fri, 23 Feb 2018 22:01:00 +0000 (UTC) Date: Fri, 23 Feb 2018 22:01:00 +0000 (UTC) From: "Ashutosh Mestry (JIRA)" To: dev@atlas.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ATLAS-2460) Data Migration: Moving Data from Earlier Versions of Atlas to Most Recent MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ATLAS-2460?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-2460: ----------------------------------- Description:=20 *Background* The most recent version of Atlas uses _JanusGraph_ as database. Earlier ver= sions used to use _Titan v0.5.4_. The formats used for storing data have ch= anged. The current version of Atlas also implement features within Atlas entities.= This makes the storages structures differ. A data migration approach thus becomes necessary to address the format inco= mpatibilities. *Approach* Earlier version of Atlas could use=C2=A0_Export_ process to extract data ou= t of the _Titan_ database. This ZIP file would then be moved to a cluster w= ith newer version of Atlas installed. An _Import_ process on the new cluste= r would update the new cluster with data migrated to the new format. It should be possible for _Data Migration_=C2=A0to be initiated from Ambari= , so that it becomes part of the Ambari's upgrade process. It should also be possible to see the status of the migration as it progres= ses. During the process, no hook messages should be processed or any notifi= cations sent out. was: *Background* The most recent version of Atlas uses _JanusGraph_ as database. Earlier ver= sions used to use _Titan v0.5.4_. The formats used for storing data have ch= anged. The current version of Atlas also implement features within Atlas entities.= This makes the storages structures differ. A data migration approach thus becomes necessary to address the format inco= mpatibilities. *Approach* Earlier version of Atlas could use=C2=A0_Export_ process to extract data ou= t of the _Titan_ database. This ZIP file would then be moved to a cluster w= ith newer version of Atlas installed. An _Import_ process on the new cluste= r would update the new cluster with data migrated to the new format. It should be possible for _Data Migration_=C2=A0to be initiated from Ambari= , so that it becomes part of the Ambari's upgrade process. =C2=A0 > Data Migration: Moving Data from Earlier Versions of Atlas to Most Recent > ------------------------------------------------------------------------- > > Key: ATLAS-2460 > URL: https://issues.apache.org/jira/browse/ATLAS-2460 > Project: Atlas > Issue Type: Improvement > Components: atlas-core > Affects Versions: trunk > Reporter: Ashutosh Mestry > Assignee: Ashutosh Mestry > Priority: Major > Attachments: ATLAS-2460-Data-Migration.patch > > > *Background* > The most recent version of Atlas uses _JanusGraph_ as database. Earlier v= ersions used to use _Titan v0.5.4_. The formats used for storing data have = changed. > The current version of Atlas also implement features within Atlas entitie= s. This makes the storages structures differ. > A data migration approach thus becomes necessary to address the format in= compatibilities. > *Approach* > Earlier version of Atlas could use=C2=A0_Export_ process to extract data = out of the _Titan_ database. This ZIP file would then be moved to a cluster= with newer version of Atlas installed. An _Import_ process on the new clus= ter would update the new cluster with data migrated to the new format. > It should be possible for _Data Migration_=C2=A0to be initiated from Amba= ri, so that it becomes part of the Ambari's upgrade process. > It should also be possible to see the status of the migration as it progr= esses. During the process, no hook messages should be processed or any noti= fications sent out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)