----------------------------

Original Description

Description:

No documentation summary in engineering ticket

Engineering Ticket Description:

As part of this ticket:

• Ensure ClusterDistinct supports readConcern level snapshot
• Ensure ClusterDistinct selects an appropriate atClusterTime based on the shards it targets, and will retry on snapshot errors
• Add unit tests verifying this works

Proposed implementation:

1. Add a supportsReadConcern to ClusterDistinct that always returns true
2. Update functions in cluster_commands_helpers.cpp to compute atClusterTime and attach it to the generated responses, like in ClusterAggregate (computing atClusterTime with computeAtClusterTime, attaching atClusterTime with appendAtClusterTime)
   • buildVersionedRequestsForTargetedShards here
   • buildUnversionedRequestsForShards here
3. snapshot errors are already retried in strategy.cpp, so there should be no work there
4. Add unit test verify requests sent by ClusterDistinct contain appropriate atClusterTimes and are retried on snapshot errors, like the existing ClusterFind tests

----------------------------

Description

Scope of changes (files that need work and how much)

• work for distinct and transactions were mainly done via DOCS-12725
• This just updated the read concern page table. Later, some reorg of the table is in order.

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)