[
https://issues.apache.org/jira/browse/OLINGO-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477130#comment-15477130
]
Steven Hawkins commented on OLINGO-1009:
----------------------------------------
> The cycle detection needs to be prevented only in the case where $levels =
> max is presented, not when say $levels=5
I don't think that is a given - it MUST be resolved with max, but I don't see
whether it CAN be in the numeric case. I'm arguing that both cases should be
handled the same as for any sufficiently large numeric expansion you would need
this behavior.
> I fixed that now and updated the test case now
Yes, that's closer now. I'd argue for using a set over a stack, but that's a
very minor concern.
> 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)
