You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Mandar Ambawane (Jira)" <ji...@apache.org> on 2022/04/01 08:12:00 UTC
[jira] [Created] (ATLAS-4576) Backward compatibility for check provided for Attribute Name in Parent and Child Type
Mandar Ambawane created ATLAS-4576:
--------------------------------------
Summary: Backward compatibility for check provided for Attribute Name in Parent and Child Type
Key: ATLAS-4576
URL: https://issues.apache.org/jira/browse/ATLAS-4576
Project: Atlas
Issue Type: Improvement
Reporter: Mandar Ambawane
Currently we have provided 2 checks for the Attribute Name:
[ATLAS-3872|https://issues.apache.org/jira/browse/ATLAS-3872]
Restrict typedef creation when a child type attribute conflicts with parent type attribute of same name
[ATLAS-4522|https://issues.apache.org/jira/browse/ATLAS-4522]
Updating typedef with new supertype should be allowed only if attributes are unique compared to other existing supertypes
But in the earlier versions these checks were not there. So there may be a chance of Atlas environment having such data where these checks can cause problems at the time:
1. Atlas Startup.
2. Creating new typedefs
This patch handles these scenarios and provides backward compatibility for these 2 changes mentioned.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)