[SERVER-8538] Deprecate $atomic/isolated update option Created: 12/Feb/13  Updated: 29/Jun/18  Resolved: 12/Dec/17

Status: Closed
Project: Core Server
Component/s: Write Ops
Affects Version/s: None
Fix Version/s: 3.6.1, 3.7.1

Type: Task Priority: Minor - P4
Reporter: Scott Hernandez (Inactive) Assignee: David Storch
Resolution: Done Votes: 1
Labels: deprecate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by DRIVERS-435 Deprecate $atomic/isolated option Closed
is depended on by SERVER-30005 remove $isolated/$atomic option Closed
Documented
is documented by DOCS-11205 Docs for SERVER-8538: Deprecate $atom... Closed
Related
is related to SERVER-1734 Rename "atomic" to "isolated" Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: Query 2017-12-18
Participants:

 Description   

This doesn't work now anyway, esp. in sharding, and maybe with new yielding.



 Comments   
Comment by Githook User [ 12/Dec/17 ]

Author:

{'name': 'David Storch', 'email': 'david.storch@10gen.com', 'username': 'dstorch'}

Message: SERVER-8538 Occasionally log a deprecation warning when $isolated/$atomic is used.

(cherry picked from commit f7b89ae89514673770f558456d15cb46581c3be5)
Branch: v3.6
https://github.com/mongodb/mongo/commit/fbc1248604839045e00d692c17db9942766fd864

Comment by Githook User [ 12/Dec/17 ]

Author:

{'name': 'David Storch', 'email': 'david.storch@10gen.com', 'username': 'dstorch'}

Message: SERVER-8538 Occasionally log a deprecation warning when $isolated/$atomic is used.
Branch: master
https://github.com/mongodb/mongo/commit/f7b89ae89514673770f558456d15cb46581c3be5

Generated at Thu Feb 08 03:17:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.