[
https://issues.apache.org/jira/browse/ATLAS-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124294#comment-17124294
]
ASF subversion and git services commented on ATLAS-3722:
--------------------------------------------------------
Commit bd9e0c91ca3d16afdc092d835c8567553d90c8bc in atlas's branch
refs/heads/branch-2.0 from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=bd9e0c9 ]
ATLAS-3722: ZipFileMigrationImporter: Allow AtlasPatchService to Run Before
Migration Starts
(cherry picked from commit 00bef883c5561596ccc2b7b1075e8379bf8ac6bb)
> 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)
