-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Closed as not planned
Closed as not planned
Copy link
Labels
ClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.CosmosService AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-author-feedbackWorkflow: More information is needed from author to address the issue.Workflow: More information is needed from author to address the issue.no-recent-activityThere has been no recent activity on this issue.There has been no recent activity on this issue.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Description
- Package Name: azure-cosmos
- Package Version: 4.9.0
- Operating System: macOs 15.4 (Apple M3)
- Python Version: 3.11
Describe the bug
when calling upsert_item to save a document, if the document includes non-ascii characters, an exception will be raised, which is
unsupported Unicode escape sequence
To Reproduce
Steps to reproduce the behavior:
- Create a test container "Users"
- Call upsert_item to save data like {"id": "1234", "partitionId": "London", "name": "なかむらし"}
Expected behavior
The document has non-ascii characters that should be saved successfully
Additional context
I believe the root cause is the implementation of _request_body_from_data function in _synchronized_request.py, which should use json.dumps with ensure-ascii=False
snigdho611-bjit
Metadata
Metadata
Assignees
Labels
ClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.CosmosService AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-author-feedbackWorkflow: More information is needed from author to address the issue.Workflow: More information is needed from author to address the issue.no-recent-activityThere has been no recent activity on this issue.There has been no recent activity on this issue.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Type
Projects
Status
Done