atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-3346) Import Service: Add support to re-activate deleted entity
Date Wed, 06 Nov 2019 11:58:00 GMT

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

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

Commit 65751b651c7d24b27aa157c0b14abe41c8143bdf in atlas's branch refs/heads/branch-0.8 from
nikhilbonte
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=65751b6 ]

ATLAS-3346:- Import Service Add support to re-activate (branch-0.8).

Signed-off-by: nixonrodrigues <nixon@apache.org>


> Import Service: Add support to re-activate deleted entity
> ---------------------------------------------------------
>
>                 Key: ATLAS-3346
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3346
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Nikhil Bonte
>            Assignee: Nikhil Bonte
>            Priority: Major
>             Fix For: 2.1.0, 3.0.0
>
>         Attachments: ATLAS-3346-Import-Service-Add-support-to-re-activate-branch-0.8-v9.patch,
ATLAS-3346-Import-Service-Add-support-to-re-activate-v4.patch
>
>
>  
> *Background:*
>          Requirement for import API is that if request contains "replicatedFrom"
option, in this case import API should activate those tables which are part of import zip
but are having state as 'deleted' in Atlas server. E.g.
>  * Consider t1...t5 under db1 replicated from source to destination using table level
incremental export from source.
>  * Next import request at destination contains only t1...t3, in such case t4 & t5
must be deleted at Destination (part of ATLAS-3416).
>  * Now next import request at destination contains t1...t4, in such case t4 & its
relationships must be re-activated at destination.
> Currently import API do not update state as ACTIVE for such entity. Logs says -
>  WARN  - [bulkImporter-1:] ~ attempt to activate deleted entity (guid=c5df6bde-a14d-4596-a484-6bece8b7f919).
Ignored (AtlasEntityStoreV2:950)
> This jira will support to re-activate deleted entity in such case.
>  
> *Solution:*
>  * In import API, while processing entity from zip, if zip has entity as ACTIVE &
Atlas server has entity as DELETED, re-activate such entity & its relationships.
>  * It is also handled that only those relationships will be activated which are present
in incoming entity's relationshipAttributes (obtained from zip).
>  
>  



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

Mime
View raw message