Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11205

Docs for SERVER-8538: Deprecate $atomic/isolated update option

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.1, 3.6.1
    • Affects Version/s: None
    • Component/s: None
    • Labels:

      Documentation Request Summary:

      This change causes the server to log the following message, including a dochub link:

      The $isolated/$atomic option is deprecated. See http://dochub.mongodb.org/core/isolated-deprecation

      The $isolated/$atomic option is being deprecated because it will be superseded by true transaction support which we are planning to release in 3.8 and 4.0. (The current plan is that 3.8 will support single replica set transactions, whereas 4.0 will support multi-shard transactions.)

      The dochub link currently redirects to https://docs.mongodb.com/manual/core/read-isolation-consistency-recency/. When transaction support gets released in the future, we should probably change the link to point to text explaining that you should use transactions instead of $isolated/$atomic.

      Do we still have $isolated/$atomic in the reference manual? If so, this page needs to indicate that this feature is deprecated as of 3.6. [nope, we already removed these pages and references]

      Engineering Ticket Description:

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

            kay.kim@mongodb.com Kay Kim (Inactive)
            kay.kim@mongodb.com Kay Kim (Inactive)
            0 Vote for this issue
            2 Start watching this issue

              6 years, 2 weeks, 1 day ago