[SERVER-43192] fix checks for missing abortIndexBuild fields during oplog application Created: 06/Sep/19 Updated: 29/Oct/23 Resolved: 07/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Execution Team 2019-09-09 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When processing abortIndexBuild entries during secondary oplog application, the server should throw an exception if the oplog entry is missing either of the following fields:
|
| Comments |
| Comment by Githook User [ 06/Sep/19 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: |