You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/02/14 17:27:00 UTC
[jira] [Commented] (ATLAS-3603) Data Migration: Auto-start zip
Migration Import
[ https://issues.apache.org/jira/browse/ATLAS-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037132#comment-17037132 ]
ASF subversion and git services commented on ATLAS-3603:
--------------------------------------------------------
Commit 3e035c45a9dd695471d0927bbcdd72108094c828 in atlas's branch refs/heads/master from Nikhil Bonte
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3e035c4 ]
ATLAS-3595, ATLAS-3603: Auto-start migration import for ZIP file-based migration.
Signed-off-by: Ashutosh Mestry <am...@cloudera.com>
> Data Migration: Auto-start zip Migration Import
> -----------------------------------------------
>
> Key: ATLAS-3603
> URL: https://issues.apache.org/jira/browse/ATLAS-3603
> Project: Atlas
> Issue Type: New Feature
> Reporter: Nikhil Bonte
> Assignee: Nikhil Bonte
> Priority: Major
>
>
> This feature will integrate with ATLAS-3595.
> Migration import should start when the data (zip) to be ingested is available at the pre-configured location.
> Approach:
> ZipMigrationImporter will first check if zip is available, accessible & completely written.
> * If yes, migration will start ingesting zip.
> * if not, will poll the location periodically. when existence is detected, import will proceed as usual.
> It uses the file size comparison approach. Once modify event is received, file size is compared in an interval. If sizes match, it means file is available and not being written.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)