Mailing-List: contact dev-help@atlas.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@atlas.incubator.apache.org
Date: Fri, 21 Apr 2017 09:25:04 +0000 (UTC)
From: "Sharmadha Sainath (JIRA)" <jira@apache.org>
To: dev@atlas.incubator.apache.org
Message-ID: <JIRA.13065818.1492766646000.16767.1492766704127@Atlassian.JIRA>
In-Reply-To: <JIRA.13065818.1492766646000@Atlassian.JIRA>
References: <JIRA.13065818.1492766646000@Atlassian.JIRA> <JIRA.13065818.1492766646626@jira-lw-us.apache.org>
Subject: [jira] [Created] (ATLAS-1743) Issue with uniqueAttribute while
 creation of entities
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 21 Apr 2017 09:25:07 -0000

Sharmadha Sainath created ATLAS-1743:
----------------------------------------

             Summary: 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)