[ https://issues.apache.org/jira/browse/ATLAS-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392000#comment-17392000 ]
ASF subversion and git services commented on ATLAS-3489: -------------------------------------------------------- Commit 803d7edd503df79d33f378e2bf26259236b3167a in atlas's branch refs/heads/branch-2.0 from Ashutosh Mestry [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=803d7ed ] ATLAS-3489: Import API: Deleted entity handling improvement. (cherry picked from commit c6ee27790db7905f8d9b5b02f2961d59cc76b5cb) > Import API: missing entity in atlas after import > ------------------------------------------------ > > Key: ATLAS-3489 > URL: https://issues.apache.org/jira/browse/ATLAS-3489 > Project: Atlas > Issue Type: Bug > Reporter: Nikhil Bonte > Assignee: Nikhil Bonte > Priority: Major > Attachments: > ATLAS-3489-Import-API-Deleted-entity-handling-improv.patch, > dup_col_deleted.zip > > > Case : > *Input :* > Consider case where input zip contains hive_table which has 2 > hive_columns with same _qualifiedName_ but different _entityStatus_. > One of the columns is _ACTIVE_ while other is _DELETED_. > *Expected Result :* > Imported table must contain 2 columns with same qualifiedName but > with different entityStatus. > *Actual Result :* > Imported table has 1 column with guid of ACTIVE column from input > zip & entityStatus as DELETED. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)