[SERVER-44390] Investigate whether we can run one DDL command per 'applyOps' Created: 04/Nov/19 Updated: 06/Dec/22 Resolved: 07/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
Today, multiple DDL commands can be specified in a single 'applyOps' command. We should investigate if there are any use cases to having this and if we can only have one DDL command run per 'applyOps'. There would be confusion on which lock mode to take for the database if we were to remove the exclusive global lock here when there are multiple DDL commands to execute. If it's possible to run one DDL command per 'applyOps' we can hold the appropriate lock mode throughout the entire operation for the database without the concern of having to switch lock modes for subsequent commands. |
| Comments |
| Comment by Githook User [ 04/Dec/19 ] |
|
Author: {'name': 'Mathew Robinson', 'username': 'chasinglogic', 'email': 'mathew.robinson@mongodb.com'}Message: |