[GODRIVER-149] Drivers should check encoded operation size on client side Created: 11/Dec/17  Updated: 07/Feb/23  Resolved: 07/Feb/23

Status: Closed
Project: Go Driver
Component/s: Wire Protocol
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Rathi Gnanasekaran Assignee: Matt Dale
Resolution: Done Votes: 0
Labels: neweng, rp-toSched
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DRIVERS-275 Drivers should check encoded operatio... Closed
Documentation Changes Summary:

1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?


 Comments   
Comment by Matt Dale [ 07/Feb/23 ]

Maximum document size is already checked in the Go driver here. Additionally, newer MongoDB versions return a reasonable error when too-large documents are sent:

(mongo.WriteException) write exception: write errors: [object to insert too large. size in bytes: 16777246, max size: 16777216]

Closing because this is done.

Comment by Bernie Hackett [ 07/Jun/21 ]

kevin.albertson, I think this was resolved by GODRIVER-150. CC rachelle.palmer

Edit - no, it wasn't. That's incoming not outgoing...

Generated at Thu Feb 08 08:33:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.