[SERVER-65001] Update timestamp query API calls for WiredTiger change Created: 28/Mar/22 Updated: 29/Oct/23 Resolved: 20/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Keith Bostic (Inactive) | 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 2022-04-18, Execution Team 2022-05-02 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
In In summary, it is now an error to set a timestamp of 0, and retrieving a timestamp that WiredTiger does not have will return a timestamp of 0 (previously, some cases returned a timestamp of 0 and some cases returned a WT_NOTFOUND error). This change breaks the MDB patch build. Here is a patch build (including the suggested changes below): https://spruce.mongodb.com/version/6241e82857e85a7c4f4a27d6/tasks Here are some suggested changes:
|
| Comments |
| Comment by Githook User [ 20/Apr/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Githook User [ 15/Apr/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Keith Bostic (Inactive) [ 28/Mar/22 ] |
|
geert.bosch, daniel.gottlieb, louis.williams: I'll mark |