[
https://issues.apache.org/jira/browse/ATLAS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299545#comment-15299545
]
ATLAS QA commented on ATLAS-664:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806076/ATLAS-664.patch
against master revision 74d9b3f.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/250//console
This message is automatically generated.
> UI: Add Support for Versioning / History
> ----------------------------------------
>
> Key: ATLAS-664
> URL: https://issues.apache.org/jira/browse/ATLAS-664
> Project: Atlas
> Issue Type: Improvement
> Affects Versions: 0.7-incubating
> Reporter: Erik Bergenholtz
> Assignee: Kalyani Kashikar
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-664.patch
>
>
> ATLAS-540 adds REST API support for fetching information about changes to
> entities stored in Atlas (this is being referred to as versioning). For each
> detailed page in Atlas, we need to expose the information provided by the
> REST API in tabular format.
> It makes sense to create a separate tab (next to "tags") on the entity
> detailed page where this information is displayed.
> The API is straightforward and can be accessed by {guid}/audit
> For more information see:
> https://github.com/apache/incubator-atlas/blob/master/webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java#L612
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
