[
https://issues.apache.org/jira/browse/ATLAS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301658#comment-15301658
]
Kalyani Kashikar commented on ATLAS-664:
----------------------------------------
Hi [~yhemanth] - wanted clarification on below given comments:
2) For Tag add event, we don't show any details. The API is passing the added
tag in the audit response. This can be parsed and shown.
3) In general, if there is a failure to parse any detail, it is better to show
the entry as a string, than not to show anything.
>> You mean we do not show Details button for ADD_TAG action?
6) A usability suggestion. Would it be better to show the actions as "Added
entity", "Added tag", "Updated entity" instead of the technical looking
ENTITY_ADDED?
>> Can I please have list of all the actions and corresponding simplified
>> labels for the same?
> 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)
