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

ASF subversion and git services commented on ATLAS-4019:
--------------------------------------------------------

Commit 8d7ac77a74479263ce59b9e22bb3def91b8b9326 in atlas's branch 
refs/heads/master from Deep Singh
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8d7ac77 ]

ATLAS-4019: audit improvement to store only delta

Signed-off-by: Madhan Neethiraj <[email protected]>


> Audit improvement to store only delta
> -------------------------------------
>
>                 Key: ATLAS-4019
>                 URL: https://issues.apache.org/jira/browse/ATLAS-4019
>             Project: Atlas
>          Issue Type: Improvement
>          Components: atlas-intg
>            Reporter: Deep Singh
>            Assignee: Deep Singh
>            Priority: Major
>
> For any entity operation after the entity is created - e.g. add a column, 
> update an attribute. - the entire updated entity is saved in Hbase audits 
> (for each operation). Only the delta between two entity states needs to be 
> stored.
> Update routine could be called for an individual entity or for a list of 
> entities. Update-request may contain a full entity object or partial 
> object(with only updated attributes or relations). There could be updates in 
> entity core attributes, relationship attributes, custom attributes, or 
> associated classifications. In all the cases today we store the entire 
> updated entity in Hbase audits. Improvement is required so that only the 
> updated information is stored in Hbase audits instead of the entire entity 
> object.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to