[SERVER-48023] Update outdated "snapshot" terminology to use "timestamp" where applicable Created: 07/May/20 Updated: 06/Dec/22 Resolved: 22/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
Throughout our code, we use the term "snapshot" when we really mean "timestamp". For example, getMinimumVisibleSnapshot(). Every operation already has a snapshot with WT, and the concept of a "named snapshot" is outdated. We should audit and change locations that use this outdated terminology. |
| Comments |
| Comment by Connie Chen [ 22/Mar/21 ] |
|
We will target to do this incrementally as we work on other tickets. |