You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Shwetha G S (JIRA)" <ji...@apache.org> on 2016/08/02 17:30:20 UTC
[jira] [Updated] (ATLAS-965) Old lineage still exists after
dropping tables and re-creating tables with same name.
[ https://issues.apache.org/jira/browse/ATLAS-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shwetha G S updated ATLAS-965:
------------------------------
Attachment: ATLAS-965.patch
Added table create time to the process created for create table operations
> 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
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-965.patch, 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)