[DOCS-12726] Docs for SERVER-40026: Blacklist distinct in sharded collections in transactions Created: 20/May/19  Updated: 13/Nov/23  Resolved: 21/May/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.12, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates DOCS-12725 Docs for SERVER-40026: Blacklist dist... Closed
Participants:
Days since reply: 4 years, 38 weeks, 2 days ago

 Description   

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

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)


Generated at Thu Feb 08 08:05:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.