[ https://issues.apache.org/jira/browse/ATLAS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223868#comment-15223868 ]
Shwetha G S commented on ATLAS-541: ----------------------------------- {quote} We use a metadata repository not just for business-metadata like catalog/glossary, but as an operational metadata store as well. In cases of operational metadata, we often tend to persist metadata more in transient form (like staging), and finally publish something which is curated/approved as the final copy for use with data lineage. So expect lot of such staged metadata which needs to be discarded permanently from the system. {quote} Would it help if we enable/disable soft delete at type level(depending on the typeName in type system), instead of at atlas system level? {quote} In my opinion, in the absence of versioning, a decent audit trail of an entity state during its lifecycle adds to the needs of regulartory governance requirements. But I am not sure how much a 'soft' delete can satisfy such governance requirements. {quote} You mean the audit trail before the entity is deleted? Haven't you had any asks of ability to search on deleted entities or the important entity types are never deleted? > 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)