You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Rahul Kurup (Jira)" <ji...@apache.org> on 2022/04/18 11:49:00 UTC

[jira] [Created] (ATLAS-4584) Possible classification scenarios requiring checks.

Rahul Kurup created ATLAS-4584:
----------------------------------

             Summary:  Possible classification scenarios requiring checks.
                 Key: ATLAS-4584
                 URL: https://issues.apache.org/jira/browse/ATLAS-4584
             Project: Atlas
          Issue Type: Bug
            Reporter: Rahul Kurup


{*}Scenario 1{*}:
1. User creates Classification 1 with attributes A(string), B(boolean), C(int). 
2. User creates Classification 2 with the same attributes as above: A,B and C.
3. User creates Classification 3 with its own unique attribute D, but also makes Classification 1 and Classification 2 as its super-classifications.
4. The resulting classification has A,B,C and D as its attributes but it is unknown which parent’s attributes are being used.

*Possible negative consequence:* It is unclear to the user as to what is the flow of inheritance of attributes being followed.

{*}Expected result{*}: A negative error message indicating that parents possess similar attribute names, denying the action. Or alternately, show in the typedef of the classification, which attributes come from which parent classifications.

{*}Scenario 2{*}:
1. User creates Classification 1 with attribute A of type string.
2. User creates Classification 2 with the same attribute name A but with type boolean.
3. User creates Classification 3 with Classification 1 and Classification 2 as its super-classifications.
4. The resulting attribute has Classification 2’s A boolean attribute, but not Classification 1’s A string attribute

{*}Possible negative consequence{*}:Because there is no check in this scenario, it may be possible that in a particularly large classification hierarchy, a parent classification may end up cannibalizing another parent classification's attributes because of their similar names and despite their different types. This would be unknown to the user creating the child classification from these parent classifications.

*Expected result:* A negative error message indicating that parents possess similar attribute names, denying the action. Or find a way to have both attributes co-exist.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)