Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.0.0-rc2
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
QO 2023-05-29
Confidence Status:
None
Work Order:
0

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

~~SERVER-76143~~ is adding the missing find command fields to the key. As a follow-up, add the remaining gen command fields:

$readPreference
readConcern
Will need to shapify the "afterClusterTime" argument to collapse any "afterClusterTime" specification to the same telemetry key.

writeConcern (happens to be rejected for find, but generically included)
apiVersion, apiStrict, apiDeprecationErrors

Though it is possible, that readConcern can be done via ~~SERVER-76553~~ or we can close that as a duplicate and accomplish it here.

depends on

SERVER-76143 Add missing fields to telemetry key

Closed

is depended on by

SERVER-85099 Tracking: Milestone 1

Closed

SERVER-85105 Tracking: PM-2885 Milestone 0

Closed

is duplicated by

SERVER-76553 Shapify readConcern's "afterClusterTime" and ensure we only use client-provided read/write concern values

Closed

is related to

SERVER-76553 Shapify readConcern's "afterClusterTime" and ensure we only use client-provided read/write concern values

Closed

Assignee:: Maddie Zechar

Reporter:: Maddie Zechar

Participants:: Githook User, Maddie Zechar

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: May 08 2023 05:48:46 PM UTC

Updated:: Feb 07 2024 07:23:55 PM UTC

Resolved:: May 23 2023 03:58:24 PM UTC

Confidence Status Last Update:: 09/May/23 6:40 PM