The Partition Key Format field is not for this.
But you can use the “Additional Partition Key Field” (on the table mapping page, might need to be added via Personalization) to overcome this. Use a field (like an account no. field) that has an even distribution across the data.
Perfect, thanks! running again 🙂
In the case where the original partition key limit was reached, what is the best way to drop and recreate the table in the destination? Is there a way to do this from Cloud Replicator, or should we do manually in CosmosDB? thanks
Unless this is a table where you need to support deletions, it doesn’t matter… Just leave it.
thanks!