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

Blacklist distinct in sharded collections in transactions

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.12
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding 2019-05-06, Sharding 2019-05-20, Sharding 2019-06-03

      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.

            Assignee:
            ilan.cohen@mongodb.com Ilan Cohen
            Reporter:
            greg.mckeon@mongodb.com Gregory McKeon (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: