[
https://issues.apache.org/jira/browse/ATLAS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348176#comment-15348176
]
Kalyani Kashikar commented on ATLAS-847:
----------------------------------------
[~shwethags] I am afraid without {{totalCount}} in the first request itself I
wont be able to create the pagination bar (which contains the number of pages)
and also for number of pages we require the pageSize.
Generally the following info would be required for creating an efficient
pagination widget:
* In the first API call OR a separate call get the following info:
** Total number of records : {{totalCount}}
** page size of table : {{pageSize}}, This can be done on client side also
* Once the {{totalCount}} is known, the pagination bar is created with number
of boxes = {{totalCount}} / {{pageSize}}
* Now if user clicks on 4th page, an API request is made with {{startKey}} =
{{pageSize}} * 4
If the {{totalCount}} is not available from the server end, creation of the
pagination bar will not be possible and only client side pagination can be
supported.
> 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
>
> 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)
