[
https://issues.apache.org/jira/browse/ATLAS-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16748421#comment-16748421
]
ASF subversion and git services commented on ATLAS-3029:
--------------------------------------------------------
Commit de7fe47a2b714a023c5aa3d4f3b5648306ae7af1 in atlas's branch
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=de7fe47 ]
ATLAS-3029, ATLAS-3020: Audit APIs for classification updates. Part-2.
> API: Retrieve Classification Events from Audits
> -----------------------------------------------
>
> Key: ATLAS-3029
> URL: https://issues.apache.org/jira/browse/ATLAS-3029
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core, atlas-intg
> Affects Versions: trunk
> Reporter: Ashutosh Mestry
> Assignee: Ashutosh Mestry
> Priority: Major
> Fix For: 2.0.0
>
> Attachments:
> ATLAS-3020-Audit-APIs-for-classification-updates-master.patch
>
>
> *Use Cases*
> 1. In the case where user looses data within Atlas, they can get it ingested
> by using tool like _import-hive_. With this approach, the user does not get
> the classifications and the entities associated with them.
> 2. In case where classifications were inadvertently removed from entities.
> *Solution*
> In the scenarios above, currently there isn't a way to know the
> classification operations performed.
> A REST API that would get this information from Atlas' Audit tables would
> benefit the user.
> *Approach Guidance*
> * REST endpoint: Use Atlas' Audit Repository to fetch the audit events. This
> API should accept a timestamp range so that useful audit events can be
> fetched.
> * REST endpoint: Re-play the audit events to update Atlas.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
