-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution NAMER
-
Fully Compatible
-
ALL
-
v7.0, v6.0
-
Execution NAMR Team 2023-08-21
The logic given in SERVER-75921 for why updates/deletes against sharded time-series collections don’t apply when updating the raw time-series buckets collection. Nonetheless, attempts to do so lead to errors like:
A single delete on a sharded time-series collection must contain the shard key (and have the simple collation).
Mongosync needs this in order to apply this algorithm for accommodating certain race conditions.
- is related to
-
SERVER-75921 Remove conflicting error message for sharded time-series single delete with an id query
- Closed
- related to
-
SERVER-80786 [7.0] Sharded time-series buckets should allow deleteOne against `_id`
- Closed