[
https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-751.
------------------------------------
Fix Version/s: 2.0.0
Resolution: Fixed
> Add support for primary key constraint on class types
> -----------------------------------------------------
>
> Key: ATLAS-751
> URL: https://issues.apache.org/jira/browse/ATLAS-751
> Project: Atlas
> Issue Type: Improvement
> Affects Versions: 0.7-incubating
> Reporter: Suma Shivaprasad
> Assignee: Suma Shivaprasad
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: ATLAS-751.1.patch, ATLAS-751.1.patch
>
>
> Persisting the qualified Name for an entity has multiple issues
> 1. In case of soft deletes,consider the following scenario
> a. Table A -> insert overwrite -> Table B
> If the table A and B are dropped and recreated again and the insert
> overwrite query is rerun, then it should create another lineage process since
> the tables are different here. Similarly for CTAS etc. However the same
> process will get updated due to the current way of storing qualifiedName
> 2. Storing qualified names inherently leads to a lot of updates during
> operations renames for eg: if a table is renames, all its
> columns.qualifiedName, sd.qualifiedName etc get updated. If this is done with
> partitions, then the updates will definitely take a lot of time.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
