You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/10/14 13:27:00 UTC

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

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

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

Commit 289c87a67a2307ea3d1b3bdceee7bc322f35a291 in atlas's branch refs/heads/master from nikhilbonte
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=289c87a ]

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

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


> Export API - connected export mismatch for lineage of entities from different DBs
> ---------------------------------------------------------------------------------
>
>                 Key: ATLAS-3451
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3451
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Nikhil Bonte
>            Assignee: Nikhil Bonte
>            Priority: Major
>         Attachments: ATLAS-3451-Export-API-connected-export-mismatch-for-lineage-of-entities-from-different-DBs-v3.patch, hive-commands-create-data.txt
>
>
> *Case 1 :*
> Data set : db1.table1 ---> process ---> db2.table2 
> Export db1.table1 with options 
> {code:java}
> {
>     "itemsToExport": [{
>       "typeName": "hive_table", "uniqueAttributes": { "qualifiedName": "db1.table1@cluster0" } 
>     }], 
>    "options": {
>         "fetchType": "connected"  
>     }
> }
> {code}
> 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
> {code:java}
> {
>     "itemsToExport": [{
>       "typeName": "hive_table", "uniqueAttributes": { "qualifiedName": "db3.table3@cluster0" } 
>     }], 
>    "options": {
>         "fetchType": "connected"  
>     }
> }
> {code}
> Expected result : exported zip should contain entities  db2, db3, db4, table2, table3, table4, p2, p3.
> Actual result : exported zip contains extra entities.
>  
>  
>  



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