[DOCS-11532] Docs for SERVER-30005: remove $isolated/$atomic option Created: 03/Apr/18 Updated: 29/Oct/23 Resolved: 01/Jun/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kay Kim (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 5 years, 36 weeks, 5 days ago | ||||||||||||
| Epic Link: | DOCS: 4.0 Server | ||||||||||||
| Description |
Documentation Request Summary:$isolated/$atomic has already been marked as deprecated, so now it can be marked as removed altogether. The one caveat worth mentioning is the upgrade/downgrade scenario since it's possible to create a partial index with $isolated in 3.4 and allowed to parse in 3.6. The following sequence of steps would crash a mongod on startup: 1. Create partial index with $isolated in 3.4 Let me know if that makes sense and feel free to follow up if it doesn't! Engineering Ticket Description:Since $isolated does not work sharded, and it doesn't provide full atomicity that people likely want when they use it, we should deprecate and then remove it once a better option exists. This ticket depends on and should only be done after |
| Comments |
| Comment by Githook User [ 01/Jun/18 ] |
|
Author: {'username': 'kay-kim', 'name': 'kay', 'email': 'kay.kim@10gen.com'}Message: Revert " This reverts commit 3513a6551f9fe6c3fc110cf8a770137945d407c0. |
| Comment by Githook User [ 01/Jun/18 ] |
|
Author: {'username': 'kay-kim', 'name': 'kay', 'email': 'kay.kim@10gen.com'}Message: |