Is there a way to force physical partitioning or replicate what happens when passing 50GB?
We need to replicate this behavior in an azure hosted dev environment.
The dev environment has a 5GB collection, while the production has passed 50GB.
This results in queries not behaving the same as the physical partitioning has a paging behavior.
We have been able to replicate in the CosmosDB Emulator by setting the throughput to a very high value.
This isn&amp;#39;t very desirable for something hosted in Azure.
So, is there a way to replicate this paging behavior in a smaller azure hosted environment?