[
https://issues.apache.org/jira/browse/ATLAS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296090#comment-15296090
]
Vimal Sharma commented on ATLAS-635:
------------------------------------
Let's consider one of the proposed solutions:
Source ----> Process(with old name) ----> Target(old entity name + marked as
delete) ---> Process(rename from old to new) ---> Target(with new entity name)
This solution will result into creation of a new entity when table is renamed.
When we create a new entity for the table, all traits and audit events
associated with original table are lost. The desirable outcome would be to
retain all traits/audit events associated with the table.
The second solution is better suited for the case. We can add a new attribute
"alias" which will maintain a list of all previous tablenames.
> 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: 0.7-incubating
> Reporter: Ayub Khan
> Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> 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)
