[
https://issues.apache.org/jira/browse/OLINGO-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876437#comment-13876437
]
Ralf Handl commented on OLINGO-27:
----------------------------------
Hello Miki,
There's no standard way to express this in OData 2.0. Some producers opted for
returning 400 Bad Request and adding a human-readable text explaining that a
filter is required and which properties to filter on,
In OData 4.0 we added the term Capabilities.FilterRestrictions to express this,
see
http://docs.oasis-open.org/odata/odata/v4.0/cos01/vocabularies/Org.OData.Capabilities.V1.xml.
You can annotate an entity set to express in a machine-readable form that
$filter is required, and which properties have to be filtered.
Regards
--Ralf
> 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)
