[JAVA-846] Deprecate all WriteResult methods that lazily call getLastError Created: 05/Jun/13  Updated: 03/Apr/14  Resolved: 16/Aug/13

Status: Closed
Project: Java Driver
Component/s: API
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: 2to3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates JAVA-900 Deprecate com.mongodb.WriteResult#get... Closed
Related
is related to JAVA-775 getLastError should ensure db.request... Closed

 Description   

There methods are inherently unreliable because they can not guarantee that the getlasterror call will return the result of the write that it claims to. It's entirely possible that another write got through on the same socket in between.

While this can currently work in concert with DB.requestStart/requestDone (since it guarantees exclusive use of the socket by one thread), that will no longer be the case if the driver implements support for SERVER-9038.


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