You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Shwetha G S (JIRA)" <ji...@apache.org> on 2016/05/19 05:42:12 UTC
[jira] [Updated] (ATLAS-716) Entity update/delete notifications
[ https://issues.apache.org/jira/browse/ATLAS-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shwetha G S updated ATLAS-716:
------------------------------
Attachment: ATLAS-716-v3.patch
Re-based to trunk. This also has changes for ATLAS-710 - the UTs were conflicting, so merged both the patches. Here are the changes:
1. Create/update/delete APIs return all the entities created/updated/deleted
2. In case of update API, and soft delete, if a struct/trait needs to be deleted, it will be hard deleted - audit will have more details
3. In case of update API, and soft delete, if an entity needs to be deleted, its just marked as deleted, and the parent entity will still have a reference to the deleted entity. For example, in case of hive model, if column has to be deleted, column will be marked as deleted and table will still have reference to this deleted column
4. In case of delete API, and soft delete, all the references(struct, trait, class) of the deleted entity are still maintained
> Entity update/delete notifications
> ----------------------------------
>
> Key: ATLAS-716
> URL: https://issues.apache.org/jira/browse/ATLAS-716
> Project: Atlas
> Issue Type: Bug
> Reporter: Shwetha G S
> Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-716-v2.patch, ATLAS-716-v3.patch, ATLAS-716.patch
>
>
> Entity delete can result in some entity updates(for reverse attributes). The listeners should be called accordingly. Also all the entities created/updated/deleted should be returned in the API response
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)