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

ASF subversion and git services commented on ATLAS-3722:
--------------------------------------------------------

Commit 00bef883c5561596ccc2b7b1075e8379bf8ac6bb in atlas's branch 
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=00bef88 ]

ATLAS-3722: ZipFileMigrationImporter: Allow AtlasPatchService to Run Before 
Migration Starts


> ZipFileMigrationImporter: Allow AtlasPatchService to Run Before Migration 
> Starts
> --------------------------------------------------------------------------------
>
>                 Key: ATLAS-3722
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3722
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>            Reporter: Ashutosh Mestry
>            Assignee: Ashutosh Mestry
>            Priority: Major
>         Attachments: 
> ATLAS-3722-Run-AtlasPatchService-before-ZipFileMigra.patch
>
>
> *Background*
> Existing implementation if _ZipFileMigrationImporter_ starts migration before 
> Java patches are applied. This is causes long patch application process to 
> happen after migration is done. This is not necessary since migration uses 
> AtlasEntity format for import.
> *Solution*
> Start migration after the service is run, that way it will not run after 
> migration completes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to