[Enter feedback here]
Please add a note that "Cross Partition OFFSET / LIMIT is not supported." to this section: https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-sql-query#OffsetLimitClause
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@VadimBurshtyn Thank you very much for the detailed feedback. I will submit a PR to be approved by the Docs Team.
@VadimBurshtyn the doc already says the following.
"Currently This clause is supported for queries within a single partition only, cross-partition queries don't yet support it."
It's not a note though, because this limitation will be removed soon, I didn't want to highlight it much. Let me know if it doesn't help
We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.
@SnehaGunda is there a date as to when this limitation will be removed? I am currently using Microsoft.Azure.DocumentDB.Core
2.4.0 and still see this error. However, I noticed in Azure CosmosDB data explorer OFFSET LIMIT
works when I make a cross partition request. Any help would be great! Thanks!
I just ran into this limitation as well. Very eager to know when the limitation will be removed.
Also waiting eagerly for this. Any comment on time-frame would be greatly appreciated
We will have full support for this in our v3 SDK which should reach GA in the next few weeks.
Thanks.
@markjbrown Is that something that won't be added in the v2? Feels like a major feature and since the single partition skip and take was added I think it would be great to have it in v2 as well.
Hi Nick. Right now it is not in plan to add to v2. If you think this is something the team should revisit I would add an issue to the v2 GitHub repo on this or +1 if there is already an issue on this.
Thanks.
If I'm not wrong, It is now supported in V3 :)
@crgarcia12 it is but many people including us are not in a position to move away from v2 anytime soon. There is just too much production code and no battle tested GA release yet.
Update. We are going to back port this to v2. Should be available by end of September or earlier.
Thanks.
Most helpful comment
@SnehaGunda is there a date as to when this limitation will be removed? I am currently using
Microsoft.Azure.DocumentDB.Core
2.4.0 and still see this error. However, I noticed in Azure CosmosDB data explorerOFFSET LIMIT
works when I make a cross partition request. Any help would be great! Thanks!