[
https://issues.apache.org/jira/browse/OLINGO-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15476398#comment-15476398
]
Christian Amend commented on OLINGO-1009:
-----------------------------------------
True when "max" is specified and the service suports this we need a cycle
detection. But does a service have to support max by default or can there be a
set number which a server can force upon the client? This would be similar to
server side paging where a service can decide to only return 10 entities and
include a next link.
[~RalfHandl] should OData services support "max" as a value for $levels by
default? Is there any way for a service to tell a client that not all levels
have been expanded? WDYT?
> Provide serilization support for $levels with $expand
> -----------------------------------------------------
>
> Key: OLINGO-1009
> URL: https://issues.apache.org/jira/browse/OLINGO-1009
> Project: Olingo
> Issue Type: New Feature
> Components: odata4-server
> Affects Versions: (Java) V4 4.0.0-beta-01
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: (Java) V4 4.3.0
>
>
> Currently Olingo parses the query with $expand with $levels construct,
> however if the payload contains the nesting of the entities, it does not
> serialize to the defined $levels
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
