[SERVER-41016] Calculate deltas for updates to large documents Created: 06/May/19 Updated: 29/Oct/23 Resolved: 23/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.14, 4.1.12, 4.0.11 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Michael Cahill (Inactive) | Assignee: | Michael Cahill (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.0, v3.6
|
||||||||||||||||||||||||||||
| Sprint: | Storage Engines 2019-05-06, Storage Engines 2019-05-20, Storage Engines 2019-06-03 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||||||
| Story Points: | 0 | ||||||||||||||||||||||||||||
| Description |
|
Use wiredtiger_calc_modify to calculate deltas for size-changing updates to large documents. |
| Comments |
| Comment by Githook User [ 31/Jul/19 ] |
|
Author: {'name': 'Michael Cahill', 'email': 'michael.cahill@mongodb.com', 'username': 'michaelcahill'}Message: (cherry picked from commit 0d16c757b7badfcadac2a6794525f3c41a621a07) |
| Comment by Githook User [ 12/Jul/19 ] |
|
Author: {'name': 'Michael Cahill', 'username': 'michaelcahill', 'email': 'michael.cahill@mongodb.com'}Message: (cherry picked from commit 0d16c757b7badfcadac2a6794525f3c41a621a07) |
| Comment by Githook User [ 23/May/19 ] |
|
Author: {'name': 'Michael Cahill', 'email': 'michael.cahill@mongodb.com', 'username': 'michaelcahill'}Message: |
| Comment by Michael Cahill (Inactive) [ 06/May/19 ] |
|
This turned up a real bug: WiredTiger's existing semantics for modifications assumes that results are committed in timestamp order. In _mdb_catalog, where updates are performed out of timestamp order, a subset of modifications would be applied, leading to invalid BSON being returned. I'll change the WT semantic to give the expected results. |