-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
Storage Execution
-
Execution Team 2019-06-17, Execution Team 2019-07-01, Execution Team 2019-07-15, Execution Team 2019-07-29, Execution Team 2019-08-12, Execution Team 2019-12-02, Execution Team 2019-12-16, Execution Team 2020-01-13, Execution Team 2020-01-27, Execution Team 2020-02-10, Execution Team 2019-12-30
-
19
We expect allowing index builds during rename collection to be fairly straightforward now that SERVER-37443 has made catalog objects survive rename collection. Conceptually, either we should only need to add {ready:false} index catalog entries to those that get updated on rename or it might just might work if the assert that no index builds are running is removed.
This task will be a little exploratory as no has taken a look at the code.
- depends on
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-31695 Support read queries across collection renames
-
- Backlog
-
- related to
-
SERVER-42494 Deadlock between aggregation pipeline and IndexBuildsCoordinator in storage engines that do not support document level locking
-
- Closed
-