[OASIS Issue Tracker] (ODATA-760) Add to depth restrictions to Capabilities Vocabulary

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63091#comment-63091 ] 

Mark Biamonte commented on ODATA-760:
-------------------------------------

From discussions in the TC call 2016-08-04, in addition to the filter restriction mentioned in the description, there are implementations that impose restrictions to:

1) the number of navigation properties that can be traversed when addressing the collection to create an entity in.
2) the number of levels that can be expanded in a $expand expression.

> Add to depth restrictions to Capabilities Vocabulary
> ----------------------------------------------------
>
>                 Key: ODATA-760
>                 URL: https://issues.oasis-open.org/browse/ODATA-760
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: Vocabularies
>    Affects Versions: V4.0_OS
>            Reporter: Michael Pizzo
>            Priority: Minor
>              Labels: Extension
>             Fix For: V4.01_WD01
>
>
> Services will likely have different limits in the number of levels of depth they support in queries.  For example:
> •	Filter on far navigation (e.g. Manager/Manager/Title eq ‘Director’ )
> •	Nested Any (e.g. Reports/any(Reports: Reports/any … )
> •	Deep expansion 1:M  (e.g. $expand=Reports, Reports/Reports)
> All those filters are syntactically correct, but create undue server-side load, so services are likely to impose limits on the number of levels of depth for such expressions.
> Is this something services should be able to report in Capabilities?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)