Support "skip" in Azure Table
MSDN says the "take" operator is only supported for the first 1,000 rows...
I need to access row number 5,000 in a highly partitioned storage layout. Support for "skip" is a requirement if we are to continue development.
Søren Nguyen Boisen commented
Oh no. I teach a course on app building with a basic introduction to creating a backend in Azure. We currently teach the students to use Table Storage for simplicity. But now I see that Table Storage is useless for larger tables since skip isn't implemented! Please implement this ancient request for basic functionality, so that I don't set up my students for failure!
This is vital to be able to use Mobile Apps with table storage and the MobileServiceIncrementalLoadingCollection from the client SDK. This collection uses skip & top to get data as needed. The fact that table storage does not allow skip, makes it impossible to use it in this scenario.
Jose Simoes commented
This is very important in scenarios such as when using the StorageDomainManager (from the Mobile App SDK). This controller make the bridging between OData requests and the Storage table.
One of the operators is the Skip. Without support from the Storage end is not possible to honour that request from the client.
Another relevant use case is when using the MobileServiceIncrementalLoadingCollection. This requires that Skip and Top exist to have that performing as expected.
Also see this request: We can accomplish something similar if we can decode/encode our own ContinuationToken