atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sharmadha Sainath (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-965) Old lineage still exists after dropping tables and re-creating tables with same name.
Date Thu, 30 Jun 2016 06:41:10 GMT

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

Sharmadha Sainath updated ATLAS-965:
------------------------------------
    Attachment: sourcetable-lineagegraph.png
                CTAStable-lineagegraph.png

Attached the screenshot of lineage graphs after recreating the tables with same name.
When new tables are re-created, new hive_process is not created as the hive_process is same
for the old tables.

> Old lineage still exists after dropping tables and re-creating tables with same name.
> -------------------------------------------------------------------------------------
>
>                 Key: ATLAS-965
>                 URL: https://issues.apache.org/jira/browse/ATLAS-965
>             Project: Atlas
>          Issue Type: Bug
>         Environment: Atlas/HBase/Solr/External Kafka
>            Reporter: Sharmadha Sainath
>            Priority: Critical
>         Attachments: CTAStable-lineagegraph.png, sourcetable-lineagegraph.png
>
>
> 1. Created tables table_1 and table_2 as ctas from table_1.
> 2. dropped tables table_1 and table_2
> (table_1 and table_2 are marked deleted)
> 3. re-created table_1
> (new table_1 had no lineage graph created. Old table_1 and table_2 had the old lineage
graph)
> 4.re-created table_2 as CTAS from table_1
> (new tables and old tables have both new and old lineage)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message