[
https://issues.apache.org/jira/browse/ATLAS-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681249#comment-17681249
]
ASF subversion and git services commented on ATLAS-4576:
--------------------------------------------------------
Commit a3636b430b19320dedf684d89331738cb5213bd0 in atlas's branch
refs/heads/branch-2.0 from Mandar Ambawane
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a3636b430 ]
ATLAS-4576 Backward compatibility for check provided for AttributeName in
Parent and Child TypeDef
Signed-off-by: Mandar Ambawane <mandar.ambaw...@freestoneinfotech.com>
> Backward compatibility for check provided for AttributeName in Parent and
> Child TypeDef
> ---------------------------------------------------------------------------------------
>
> Key: ATLAS-4576
> URL: https://issues.apache.org/jira/browse/ATLAS-4576
> Project: Atlas
> Issue Type: Improvement
> Reporter: Mandar Ambawane
> Assignee: Mandar Ambawane
> Priority: Major
>
> 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.10#820010)
