[
https://issues.apache.org/jira/browse/ATLAS-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3603:
--------------------------------
Fix Version/s: trunk
> 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
> Fix For: trunk
>
> Attachments: ATLAS-3595-ATLAS-3603-Auto-start-migration-import.patch
>
>
>
> 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)