[
https://issues.apache.org/jira/browse/ATLAS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232501#comment-15232501
]
Suma Shivaprasad commented on ATLAS-528:
----------------------------------------
Had intended to remove DROPVIEW_PROPERTIES earlier since I had noticed that the
hive parser doesnt result in this HIveOperation enum type in any way while
trying to come up with a test case for it . It is an extra unused
HiveOperation in hive code. Had missed removing it. Thanks for catching this.
Will upload the patch again after removing this
> support drop table, view
> ------------------------
>
> Key: ATLAS-528
> URL: https://issues.apache.org/jira/browse/ATLAS-528
> Project: Atlas
> Issue Type: Sub-task
> Affects Versions: 0.7-incubating
> Reporter: Suma Shivaprasad
> Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-528.1.patch, ATLAS-528.patch
>
>
> Drop table and view requires soft deletes. The reason is whenever a table is
> dropped , it also may have an associated lineage which consists of a
> hive_process which N input tables and an output table. If the table is
> dropped, the lineage edge is also dropped resulting in incorrect lineage
> history.
> With soft deletes, the expected behaviour is to changes the table status to
> "deleted" and when the table is recreated through a create table statement,
> then create another vertex/entity for that table with the new state. Also,
> the lineage for this newly recreated table should be a new hive_process and
> should not reuse the existing entity/vertex even though the hive statement
> for that process is the same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
