[
https://issues.apache.org/jira/browse/OLINGO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876414#comment-13876414
]
M Carissimi commented on OLINGO-27:
-----------------------------------
Hello,
we are building our own provider which queries data from the database (without
the use of JPA) and we have similar questions about pagination and limitation
of the maximum number of rows returned by a data set.
Pagination seems to work well using the 'next' links with the number of skip
tokens to use. Unfortunately we have seen that some OData Consumers (i.e. Power
Pivot for Microsoft Excel) simply follow the 'next' link in all the pages to
retrieve all the data in a table. When there is a large number of rows in a
table, this becomes an issue.
Is there a way to avoid returning the whole data set (in separated pages) and
indicate to a consumer that more data is available but that it needs to be
requested in a different way (i.e. using filters)?
Cheers
Miki
> JPA server side paging
> ----------------------
>
> Key: OLINGO-27
> URL: https://issues.apache.org/jira/browse/OLINGO-27
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-jpa
> Affects Versions: V2 1.1.0
> Environment: OS X, Linux, Windows
> Reporter: Carl J. Mosca
> Assignee: Chandan V.A
> Priority: Blocker
> Labels: paging
>
> Server side paging is required for our use case. A configurable hard-limit
> on page size is also needed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
