Blacklist distinct in sharded collections in transactions

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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
            Reporter:
            Gregory McKeon (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: