atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-528) support drop table, view
Date Fri, 08 Apr 2016 17:21:25 GMT

     [ https://issues.apache.org/jira/browse/ATLAS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Suma Shivaprasad updated ATLAS-528:
-----------------------------------
    Attachment: ATLAS_528.2.patch

Attaching after rebasing with trunk and removing DROPVIEW_PROPERTIES

> 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, ATLAS_528.2.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)

Mime
View raw message