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/02/02 05:35:00 UTC
[jira] [Created] (ATLAS-4547) Classification behaviour is not working as expected (overwriting attribute values and deleted entities)
Rahul Kurup created ATLAS-4547:
----------------------------------
Summary: Classification behaviour is not working as expected (overwriting attribute values and deleted entities)
Key: ATLAS-4547
URL: https://issues.apache.org/jira/browse/ATLAS-4547
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
Scenario 1:
If a classification attribute of either type 'string' or type 'array<string>' is marked as isOptional : false, then that field is a mandatory field and has to have some value filled in when assigned to an entity.
Assume that an a classification with such an attribute is already assigned to an entity. Then it is observed that if a request is fired using the PUT request to the API {{api/atlas/v2/entity/guid/<guid>/classifications}} such that the value of that classification attribute is a blank value, it is accepted and the attribute value becomes blank even though it is a mandatory attribute.
Scenario 2:
It is possible to assign a classification to an entity deleted by a request to the bulk delete API {{api/atlas/v2/entity/bulk}} or a DELETE request to the entity API {{api/atlas/v2/entity/guid/}}, even though this behaviour is not allowed by the Atlas UI.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)