-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
QE 2025-12-08
-
None
-
None
-
None
-
None
-
None
-
None
-
None
For both performance and correctness reasons, we should stop serializing inserts/updates/deletes as bulkWrites internally with the write batch executor. Correctness wise, this is needed because bulkWrite does not support legacy runtime constants (this causes a test failure in jstests/noPassthrough/query/update/update_now_clustertime_sharding.js)
Note that to keep the response processor logic simple, we will want to convert the inserts/updates/deletes to BulkWriteResponses.
- related to
-
SERVER-114725 Investigate failure in resharding_retryable_writes.js
-
- Open
-
-
SERVER-115761 add batch size estimation for batched commands
-
- In Progress
-
-
SERVER-114998 make sure UWE is resilient to concurrecnt collection drops while executing a shard key update
-
- Needs Scheduling
-