[SERVER-63201] Relax restriction of deletion ops in applyOps command. Created: 28/Dec/21 Updated: 29/Oct/23 Resolved: 10/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0, 5.0.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Huan Li | 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 | ||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||||||||||||||||||||||||||||||
| Sprint: | Execution Team 2022-02-21 | ||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 150 | ||||||||||||||||||||||||||||||||||||||||
| Description |
| Comments |
| Comment by Githook User [ 07/Mar/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Githook User [ 10/Feb/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Huan Li [ 01/Feb/22 ] |
|
daniel.gottlieb redbeard0531 Just wanna make sure this is not fall out of the attention. Could the server team work on this ticket or do you prefer a new SERVER ticket for this issue? Thanks! |
| Comment by Jessica Sigafoos [ 11/Jan/22 ] |
|
Let's ask server is applyops can do the deletes on capped collections. We can also see if the delete oplog entries indicate that they're from a capped collection in any way – if so the other options are more feasible. |
| Comment by Jessica Sigafoos [ 04/Jan/22 ] |
|
We could ignore the deletions in the restore, or we could not export the deletions in the dump. |