[
https://issues.apache.org/jira/browse/ATLAS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246957#comment-15246957
]
Suma Shivaprasad commented on ATLAS-635:
----------------------------------------
[~ayubkhan] Will be adding a new attribute aliases = list<string> in hive_table
as per [~yhemanth]'s suggestion to resolve this. Agree with [~yhemanth] that
the Data lineage doesnt change here with the table being renamed and hence
having an alias with the old table name should suffice. Since it could be
renamed multiple times, having a list of aliases.
> Process showing old entity name where as actual entity is renamed.
> ------------------------------------------------------------------
>
> Key: ATLAS-635
> URL: https://issues.apache.org/jira/browse/ATLAS-635
> Project: Atlas
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Ayub Khan
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> Process showing old entity name where as actual entity is renamed.
> Example:
> 1. Create table as select.
> 2. Rename the target table to new name.
> 3. Now check the lineage: The process is still showing the old table name
> where as the target table is changed. This is confusing from customer
> perspective.
> One possible solution is:
> Source ----> Process(with old name) ----> Target(old entity name + marked
> as delete) ---> Process(rename from old to new) ---> Target(with new entity
> name).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
