[ATLAS-751] Add support for primary key constraint on class types

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7-incubating
• Fix Version/s: 2.0.0
• Assignee: Suma Shivaprasad
• Reporter: Suma Shivaprasad
• Created: 05/May/16 15:52
• Updated: 17/Jun/22 20:49
• Resolved: 17/Jun/22 20:49

Description

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.

Issue Links

• is fixed by: ATLAS-3043 Unique attributes constraint at store-level