[SERVER-43794] Change MongoDB backup cursor API to include offset/length ranges Created: 03/Oct/19 Updated: 29/Oct/23 Resolved: 17/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, 4.2.4 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Daniel Gottlieb (Inactive) |
| 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: |
v4.2
|
||||
| Sprint: | Execution Team 2019-10-07, Execution Team 2019-10-21 | ||||
| Participants: | |||||
| Description |
|
The efficient backup project will dictate to consumers what bytes need to be copied from files while a backup cursor is open. Even though WT does not yet provide that information, the server can trivially generate responses that say "copy everything". Generating responses in this new schema will allow other teams to work on integrating the new format. |
| Comments |
| Comment by Githook User [ 25/Feb/20 ] |
|
Author: {'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: (cherry picked from commit cff25ee25c1ad064777c9e8ad58d36857e73035e) |
| Comment by Githook User [ 25/Feb/20 ] |
|
Author: {'username': 'dgottlieb', 'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: (cherry picked from commit 0c48b2e606a477f1744c249be765453f4cd25e08) |
| Comment by Githook User [ 17/Oct/19 ] |
|
Author: {'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: |
| Comment by Githook User [ 17/Oct/19 ] |
|
Author: {'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: |