You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Le Ma (JIRA)" <ji...@apache.org> on 2019/02/28 22:55:00 UTC

[jira] [Resolved] (ATLAS-989) Modify import-hive to use entity state

     [ https://issues.apache.org/jira/browse/ATLAS-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Le Ma resolved ATLAS-989.
-------------------------
    Resolution: Invalid

This Jira is invalid because Atlas has already used attributes to find entities by calling getEntityByAttribute() before creating a new one, which goes through api/atlas/v2/entity/uniqueAttribute/type/. Thanks.

 

> Modify import-hive to use entity state
> --------------------------------------
>
>                 Key: ATLAS-989
>                 URL: https://issues.apache.org/jira/browse/ATLAS-989
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Shwetha G S
>            Assignee: Le Ma
>            Priority: Critical
>
> Import hive currently uses DSL queries to check if entity exists and DSL query doesn't use entity state. This will not work with soft deletes in which case DSL returns deleted entity as well. Instead of DSl query, import hive can use get entity by unique attribute which filters deleted entities



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)