You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/nosql/troubleshoot-bad-request.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,16 @@ A response with this error means you are executing an operation and passing a pa
47
47
### Solution
48
48
Send the partition key value parameter that matches the document property value.
49
49
50
+
## Numeric partition key value precision loss
51
+
On this scenario, it's common to see errors like:
52
+
53
+
*The requested partition key is out of key range, possibly because of loss of precision of partition key value*
54
+
55
+
A response with this error is likely to be caused by an operation on a document with a numeric partition key whose value is outside what is supported by Azure Cosmos DB. See [Per-item limits](/azure/cosmos-db/concepts-limits#per-item-limits) for the maximum length of numeric property value.
56
+
57
+
### Solution
58
+
Consider using type `string` for partition key if requiring precise numeric values.
59
+
50
60
## Next steps
51
61
*[Diagnose and troubleshoot](troubleshoot-dotnet-sdk.md) issues when you use the Azure Cosmos DB .NET SDK.
52
62
* Learn about performance guidelines for [.NET v3](performance-tips-dotnet-sdk-v3.md) and [.NET v2](performance-tips.md).
0 commit comments