-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
None
-
None
-
None
-
None
-
None
-
None
-
None
- for the already in transaction case we can potnetially just call documentShardKeyUpdateUtil::updateShardKeyForDocument() instead of constructing and sending operations manually
- this would also remove the need for constructing SyntheticCommandInfo potentially
- alternatively we could make a new batch type and/or response type to split non-transaction and transaction cases
- related to
-
SERVER-114998 make sure UWE is resilient to concurrecnt collection drops while executing a shard key update
-
- Needs Scheduling
-