[
https://issues.apache.org/jira/browse/ATLAS-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2460:
------------------------------------
Affects Version/s: (was: trunk)
1.0.0
Fix Version/s: 1.0.0
Committed to master:
- http://git-wip-us.apache.org/repos/asf/atlas/commit/3ded3ee2
- http://git-wip-us.apache.org/repos/asf/atlas/commit/9368c8a0
- http://git-wip-us.apache.org/repos/asf/atlas/commit/5bccaa64
> 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: 1.0.0
> Reporter: Ashutosh Mestry
> Assignee: Ashutosh Mestry
> Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2460-GraphSON-Migration-6.patch,
> ATLAS-2460-HA-Mode-fix.patch
>
>
> *Background*
> The most recent version of Atlas uses _JanusGraph_ as database. Earlier
> versions 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 entities.
> This makes the storages structures differ.
> A data migration approach thus becomes necessary to address the format
> incompatibilities.
> *Approach*
> Earlier version of Atlas could use _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 cluster
> would update the new cluster with data migrated to the new format.
> It should be possible for _Data Migration_ to 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
> progresses. During the process, no hook messages should be processed or any
> notifications sent out.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
