Major Description
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).
