[
https://issues.apache.org/jira/browse/OLINGO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807930#comment-13807930
]
Georgi commented on OLINGO-27:
------------------------------
Yes, sounds reasonable to avoid choking the service with large data sets. I
think odata4j had such property - maxResults.
JPA has a setMaxResults method in its Query API for that purpose. Perhaps it
could be of use. Let the experts speak :-)
+1 from me, but I don't see this as a blocker really.
> 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: 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#6144)
