[DRIVERS-435] Deprecate $atomic/isolated option Created: 21/Dec/17  Updated: 28/Oct/23  Resolved: 07/Jun/18

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Rathi Gnanasekaran Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on NODE-1427 Deprecate $atomic/isolated option Closed
depends on RUST-89 Deprecate $atomic/isolated option Closed
depends on CSHARP-2252 Deprecate $atomic/isolated option Closed
depends on CXX-1566 Deprecate $atomic/isolated option Closed
depends on GODRIVER-385 Deprecate $atomic/isolated option Closed
depends on SERVER-8538 Deprecate $atomic/isolated update option Closed
Server Compat: 3.6, 3.7, 4.0
Start date:
Driver Compliance:
Key Status/Resolution FixVersion
NODE-1427 Works as Designed
SCALA-395 Done 2.4.0
CSHARP-2252 Fixed
CXX-1566 Works as Designed 3.3.0-rc0
GODRIVER-385 Gone away
RUST-89 Works as Designed
SWIFT-443 Done

 Description   

MongoDB 4.0 will remove these options. Drivers need to deprecate the option if there is any explicit support and document the server version limitation for users.

The definition and behavior of $isolated option is documented here : https://docs.mongodb.com/v3.2/reference/operator/update/isolated/



 Comments   
Comment by Daniel Aprahamian (Inactive) [ 27/Apr/18 ]

Node does not do anything special to support this, so no update needed.

Comment by A. Jesse Jiryu Davis [ 20/Mar/18 ]

Nothing to do for libmongoc.

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