[ https://issues.apache.org/jira/browse/ATLAS-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978558#comment-15978558 ]
Ayub Pathan commented on ATLAS-1743: ------------------------------------ Thats right [~ssainath]. Atlas will check the GUID also if it is provided in the POST body. If it is not then it will check for unique attribute: qualifiedName and the appropriate action. [~davidrad] POST can be used for both create and update. https://spring.io/understanding/REST#post > Issue with uniqueAttribute while creation of entities > ----------------------------------------------------- > > Key: ATLAS-1743 > URL: https://issues.apache.org/jira/browse/ATLAS-1743 > Project: Atlas > Issue Type: Bug > Components: atlas-core > Affects Versions: 0.8-incubating, 0.9-incubating > Reporter: Sharmadha Sainath > > Atlas allows creation of entities with same value for unique attributes. > For example , > 1. Created an hdfs_path entity with > * name = dir1 > * qualifiedName = "userdir@cl1" > * path = /user/user1/dir > Entity is created successfully. > 2. Created another hdfs_path entity with > * name = dir2 > * qualifiedName = "userdir@cl1" > * path = /user/user2/dir > Qualified Name is uniqueAttribute and entity creation with same Qualified > Name is allowed. > Problem is when the 2nd hdfs_path entity is created , 1st entity is updated > with 2nd entity's values , hence 2nd entity creation is merely an update call > here instead of a create call because of same unique attribute. > There is no condition to check uniqueness of attributes while creation of > entities which is causing the problem. > If 1st hdfs_path entity is DELETED , then 2nd hdfs_path entity POST call > creates new entity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)