[ATLAS-3451] Export API - connected export mismatch for lineage of entities from different DBs

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Assignee: Nikhil P Bonte
• Reporter: Nikhil P Bonte
• Created: 09/Oct/19 10:05
• Updated: 04/Aug/21 13:40
• Resolved: 28/Oct/19 19:44

Description

Case 1 :

Data set : db1.table1 ---> process ---> db2.table2 

Export db1.table1 with options 

{
    "itemsToExport": [{
      "typeName": "hive_table", "uniqueAttributes": { "qualifiedName": "db1.table1@cluster0" } 
    }], 
   "options": {
        "fetchType": "connected"  
    }
}

Expected result : exported zip should contain entities  db1, db2, table1, table2, process.

Actual result : exported zip does not contain db2.

 

---

Case 2 :

Data set : db1.table1 --> p1 ---> db2.table2 ---> p2 ---> db3.table3 ---> p3 ---> db4.table4 --> p4 ---> db5.table5

Export db3.table3 with options

{
    "itemsToExport": [{
      "typeName": "hive_table", "uniqueAttributes": { "qualifiedName": "db3.table3@cluster0" } 
    }], 
   "options": {
        "fetchType": "connected"  
    }
}

Expected result : exported zip should contain entities  db2, db3, db4, table2, table3, table4, p2, p3.

Actual result : exported zip contains extra entities.

 

 

 

Issue Links

• links to: Review request