You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I create a glossary with qualified name "aaaa" and then create an asset using asset manager with the same qualified name.
It does not fail . The code gets the existing Entities to check using
So the code will only find an existing entity if the type is the same. I though qualified names were supposed to be unique across entities not within a type.
Expected Behavior
I would expect the generic handler check for existing entity of the same qualified Name of a different type to stop the creation of a subsequent entity.
Steps To Reproduce
create a glossary with qualified name aaa. Then using the asset manager OMAS to create a new asset , it will incorrectly create.
I suspect that the checking of the unique attribute should be in the scope of the type in which it is defined. For example qualifiedName should check all referenceables and not the sub type.
The text was updated successfully, but these errors were encountered:
davidradl
changed the title
[BUG] Using asset manager OMAS it is possible to create an asset using an qualifiedName
[BUG] Using asset manager OMAS it is possible to create an asset using an qualifiedName that already exists
Dec 7, 2022
This is not a specific Asset Manager OMAS issue - it is common to most OMASs that use the generic handlers. Currently the design is that the qualified name is unique within the element's type. This issue proposes to change the design to expect uniqueness across the common super-type - ie Referenceable.
I think it is a good suggestion to change the design here, however, because it may be easier when we are querying relationships that return any common referenceable.
This is a break in backward compatilbility. Changing the design may cause some existing use cases to fail. So when you make this change make sure that you add information to the release notes.
davidradl
changed the title
[BUG] Using asset manager OMAS it is possible to create an asset using an qualifiedName that already exists
[BUG] Using the generic handlers, it is possible to create an asset using an qualifiedName that already exists
Dec 8, 2022
Existing/related issue?
No response
Current Behavior
I create a glossary with qualified name "aaaa" and then create an asset using asset manager with the same qualified name.
It does not fail . The code gets the existing Entities to check using
So the code will only find an existing entity if the type is the same. I though qualified names were supposed to be unique across entities not within a type.
Expected Behavior
I would expect the generic handler check for existing entity of the same qualified Name of a different type to stop the creation of a subsequent entity.
Steps To Reproduce
create a glossary with qualified name aaa. Then using the asset manager OMAS to create a new asset , it will incorrectly create.
Environment
Any Further Information?
I suspect that the checking of the unique attribute should be in the scope of the type in which it is defined. For example qualifiedName should check all referenceables and not the sub type.
The text was updated successfully, but these errors were encountered: