'Skip' limit should be far higher - int.MaxValue
'Skip' is limited to 100,000 - which makes it impossible to iterate over an entire dataset, unless there's some meaningful way to segment the data set first.
Given there's an upper limit on the complexity of the queries we can pass in 4500 chars (it seems?)
It's very, very awkward to perform tasks on large complex datasets.
Thank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
There are major performance implications for supporting this which we will need to work through.
Azure Search Product Team
Is there any solution for the case when I have to 'skip' items more than 100,000 for paging?
The workaround with the ordering only works as long as you don't need to order by another field.
Scott Louvau commented
If you have any unique field you can sort on, you can do paging with that instead to get around paging limitations.
[SELECT * FROM Items ORDER BY ID ASC]
... [Last ID is 1024]
SELECT * FROM Items WHERE ID > 1024 ORDER BY ID ASC]
A few sample ways available in industry