-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:None
Description
Description:
The "distinct" command is disallowed on sharded collections in a multi-document transaction. Attempting to use it will return OperationNotSupportedInTransaction. Distinct on unsharded collections is still allowed.
Engineering Ticket 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.
Scope of changes
- txn page
- txn operations page
- table of crud operations
- distinct command + db.collection.distinct page
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
- documents
-
SERVER-40026 Blacklist distinct in sharded collections in transactions
- Closed
- is depended on by
-
SERVER-41239 Link to recommended alternative in error message for distinct on sharded coll in txn
- Closed
- is duplicated by
-
DOCS-12726 Docs for SERVER-40026: Blacklist distinct in sharded collections in transactions
- Closed