[
https://issues.apache.org/jira/browse/ATLAS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229749#comment-15229749
]
Prasad S Madugundu commented on ATLAS-541:
-------------------------------------------
Hi Shwetha, as per your comment:
------------------
Yes, the plan is to push the status predicate to the gremlin query. But,
because of short time that we have now, we will do predicate push later.
-----------------
If you do partial implementation of soft delete (in other words, queries return
soft deleted instances as well), then I think the option to disable soft delete
is must. At least, we should be able to disable at system level.
As Cassio mentioned, option to enable/disable soft delete at type is
preferable. A better approach could to provide the capability to group the
types into packages and give the option to enable/disable soft delete at the
package level, so that we can enable only for the packages that requires audit
ability as per the data governance requirements.
I think providing the run time option would be useful in the scenarios where we
do not want to store the deleted objects for casual users (or users in trial
period). I think this gets low priority compared to the above.
> Soft deletes
> ------------
>
> Key: ATLAS-541
> URL: https://issues.apache.org/jira/browse/ATLAS-541
> Project: Atlas
> Issue Type: New Feature
> Reporter: Shwetha G S
> Assignee: Shwetha G S
>
> We don't have graph versioning currently and hard deletes are not acceptable
> for data governance. This jira tracks the proposal for soft deletes which can
> mark an entity as deleted and by default search should return only active
> entities. However, there should be an option to retrieve deleted entities
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
