[SERVER-55411] Enable create_capped_collection*.js for incremental backups Created: 22/Mar/21 Updated: 29/Oct/23 Resolved: 23/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Execution Team 2021-05-03 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Capped collections perform un-timestamped writes to delete expired documents, but all documents will have had an assigned timestamp when first inserted. This breaks contracts with the storage engine regarding mixed-use timestamps. This ticket is to evaluate whether it's safe to re-enable capped collection tests for incremental backups after |
| Comments |
| Comment by Githook User [ 23/Apr/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |