You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Suma Shivaprasad (JIRA)" <ji...@apache.org> on 2016/04/07 01:20:25 UTC
[jira] [Commented] (ATLAS-528) support drop table, view
[ https://issues.apache.org/jira/browse/ATLAS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229315#comment-15229315 ]
Suma Shivaprasad commented on ATLAS-528:
----------------------------------------
This is dependent on patch of ATLAS-527 which is under review. Hence not making it Patch Available.
> support drop table, view
> ------------------------
>
> Key: ATLAS-528
> URL: https://issues.apache.org/jira/browse/ATLAS-528
> Project: Atlas
> Issue Type: Sub-task
> Reporter: Suma Shivaprasad
> Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
> Attachments: 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)