[jira] [Updated] (ATLAS-965) Old lineage still exists after dropping tables and re-creating tables with same name.

["Madhan Neethiraj (JIRA)" <ji...@apache.org>]

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

Madhan Neethiraj updated ATLAS-965:
-----------------------------------
    Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/4ace116e9b9edfc2a16d174b5967fdea0a965cc9

> 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
>            Assignee: Shwetha G S
>            Priority: Critical
>             Fix For: 0.8-incubating, 0.7.1-incubating
>
>         Attachments: ATLAS-965.1.patch, 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)