[
https://issues.apache.org/jira/browse/ATLAS-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4522:
--------------------------------------
Fix Version/s: 3.0.0
2.3.0
> Updating typedef with new supertype should be allowed only if attributes are
> unique compared to other existing supertypes
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: ATLAS-4522
> URL: https://issues.apache.org/jira/browse/ATLAS-4522
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Radhika Kundam
> Assignee: Radhika Kundam
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> 1.Typedef1 with attributes \{a,b,c}
> 2. Typedef2 with attributes \{d} and superType\{Typedef1}
> 3. We created entities for these and everything is fine until here
> 4. Typedef3 with attributes\{a,b,c} => Attributes are same as Typedef1
> 5. Now we updated Typedef2 with one more supertype as below
> Typedef2 with superType\{Typedef1, Typedef3}
> 6. All the Typedef2 entities are having \{a,b,c} attribute values as null and
> because of that when user is searching entity of Typedef2 by it's name not
> returning the result.
> Root cause of the issue is that attributes in Typedef2 from SuperType-
> Typedef1 be overridden by SuperType-Typedef2 attributes as attribute names
> are same for Typedef1 & Typedef2
> Updating typedef with new super types should be allowed only if attributes of
> new supertype are unique and not present in any other existing supertypes.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
