[SERVER-76658] Make bulkWrite override not flush on allowed commands Created: 28/Apr/23 Updated: 29/Oct/23 Resolved: 07/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sean Zimmerman | Assignee: | Sean Zimmerman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | milestone-4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Repl 2023-05-29, Repl 2023-06-12 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The bulkWrite override can currently support multiple crud ops in succession, but any op run between will cause a batch flush. There are likely a number of commands that can be whitelisted to be able to run without flushing a current batch. This ticket should identify them and write the appropriate code to allow their execution without flush |
| Comments |
| Comment by Githook User [ 07/Jun/23 ] |
|
Author: {'name': 'seanzimm', 'email': 'sean.zimmerman@mongodb.com', 'username': 'seanzimm'}Message: |