Unless Openui5 adds capability, then odata2sparql will need to provide a configurable limit if $top is not specified.
OpenUI5 odata.v4.ODataModel#methods/bindContext "OData V4 only allows $count, $filter, $levels, $orderby and $search inside resource paths that identify a collection. In our case here, this means you can only use them inside $expand."
Is there any reason why $top, $skip, and $orderby are not supported?
Are there plans to support these?
The business reason is that $expand'ed content might be very lengthy so it is not performant to return all of the $expand'ed records.
Unless Openui5 adds capability, then odata2sparql will need to provide a configurable limit if $top is not specified.
OpenUI5 odata.v4.ODataModel#methods/bindContext "OData V4 only allows $count, $filter, $levels, $orderby and $search inside resource paths that identify a collection. In our case here, this means you can only use them inside $expand." Is there any reason why $top, $skip, and $orderby are not supported? Are there plans to support these? The business reason is that $expand'ed content might be very lengthy so it is not performant to return all of the $expand'ed records.