[ 
https://issues.apache.org/jira/browse/ATLAS-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169095#comment-15169095
 ] 

Shwetha G S commented on ATLAS-493:
-----------------------------------

This jira will just support audit functionality which will list the changes for 
an entity over time by storing the update details in key-value store. This will 
not support graph traversal at some time in the past.

The entity history will capture the following fields - timestamp, user, 
action(attribute update,tag add, tag delete), details(verbose details of the 
update). The details will contain the actual attribute updated/tag added etc. 
The audit API takes entity id as argument and returns the latest n audit 
entries and the timestamp of the next available audit entry for that entity(for 
pagination).



> Entity Versioning Support - Audit only
> --------------------------------------
>
>                 Key: ATLAS-493
>                 URL: https://issues.apache.org/jira/browse/ATLAS-493
>             Project: Atlas
>          Issue Type: New Feature
>    Affects Versions: 0.7-incubating
>            Reporter: Erik Bergenholtz
>            Assignee: Shwetha G S
>             Fix For: 0.7-incubating
>
>
> General Use Case
> Atlas must be able to track the evolution of assets as they change. Each 
> evolution (or version) of each asset must be recorded in order to track 
> lineage
> Delete Use Case
> If an asset is deleted, the asset should not show up searches unless 
> explicitly searched for.
> Requirements
> Be able to show changes over time to be implemented through Audit Log
> Requires API support to retrieve history



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to