Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-40026

Blacklist distinct in sharded collections in transactions

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.12
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 2019-05-06, Sharding 2019-05-20, Sharding 2019-06-03

      Description

      Per Alyson Cabral, we should do this.

      This is because distinct is the only command currently allowed in a sharded transaction that does not filter orphaned documents.

        Attachments

          Issue Links

          is documented by

          Task - A task that needs to be done. DOCS-12725 Docs for SERVER-40026: Blacklist distinct in sharded collections in transactions

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-41239 Link to recommended alternative in error message for distinct on sharded coll in txn

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              jack.mulrow Jack Mulrow
              Reporter:
              greg.mckeon Gregory McKeon (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: