[
https://issues.apache.org/jira/browse/ATLAS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224193#comment-15224193
]
David Kantor edited comment on ATLAS-622 at 4/4/16 2:15 PM:
------------------------------------------------------------
I agree with Venkat that hard delete is a requirement, and that soft delete
should be optional. Any soft delete implementation should be transparent to
applications i.e. Atlas would filter out soft-deleted entities from query
results and applications would not need to implement any filtering. I also
agree that there should a purge utility or API to physically remove
soft-deleted entities.
was (Author: dkantor):
I agree with Venkat that hard delete is a requirement, and that soft delete
should be optional. Any soft delete implementation should be transparent to
applications i.e. Atlas would filter out soft-deleted entities from query
results and applications would not need to implement any filtering.
> Introduce soft delete
> ---------------------
>
> Key: ATLAS-622
> URL: https://issues.apache.org/jira/browse/ATLAS-622
> Project: Atlas
> Issue Type: Sub-task
> Reporter: Shwetha G S
> Assignee: Shwetha G S
>
> Currently, in entity delete API, the entity and its related
> entities(composite entities) are deleted and there is no trace of it in the
> system. Instead, change delete to mark the entities to be deleted with
> state=DELETED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
