"$skip" and "$skiptoken"

[Filipe Rui]

Hello,


I just realized the odata4j entities iterator uses $skiptoken along
with $skip in the same request, as long as there is a $skip attribute
in the first place (originally defined in the query).

Is this the right behavior. Consider this:

http://services.odata.com/XXX?$skiptoken=9,9,10107&$skip=80

The iterator will reach the end of the server side query entry limit
(let's assume it's 10) and advance to the next set of results provided
in the "next" link. However, it will also skip 80 entries on top of
it.


Am I missing something?

[Alexey Syomichev]

I ran into the same issue, and it looks like a bug to me: $skip should be applied to the initial request only, and subsequent feed replenishment requests should have $skiptoken only, otherwise the resulting entity set has a $skip-sized hole at the beginning of each feed fragment (fragment size, maxResult, is service implementation dependent). Is there an outstanding entry in the issue tracker for this? 

--Alexey