[
https://issues.apache.org/jira/browse/ATLAS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311740#comment-15311740
]
Hemanth Yamijala commented on ATLAS-847:
----------------------------------------
{{EntityResource.getAuditEvents}} has the documentation on how to fetch
additional events. In specific, AFAIK, the steps to be followed are:
(Assuming we want to get 100 events in every call)
* Make a call to get 101 events, by setting the query parameter {{count}} to
101.
* Assuming 101 events are received, show the first 100 events, but remember the
101st event received.
* The next API call needs to set the {{startKey}} parameter to the 101st event,
and repeat from the first step.
* Things will stop when the API call gets fewer than the requested number of
items.
Hope this helps to develop the solution.
> UI: Audit versioning does not paginate details from Atlas server
> ----------------------------------------------------------------
>
> Key: ATLAS-847
> URL: https://issues.apache.org/jira/browse/ATLAS-847
> Project: Atlas
> Issue Type: Bug
> Affects Versions: 0.7-incubating
> Reporter: Hemanth Yamijala
> Assignee: Kalyani Kashikar
> Fix For: 0.7-incubating
>
>
> In ATLAS-664, the capability to view Audit events was added to the Atlas
> admin UI. However, currently, the API call made only fetches the first 100
> events (which is the default if no count is sent). In order to fetch the next
> set of events, further API calls need to be made to the Audit API, by
> providing additional parameters in the API. This JIRA is to track the
> required changes in UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
