[DRIVERS-2694] Clarify lastWrite in the max-staleness spec Created: 16/Aug/23 Updated: 22/Aug/23 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | Max Staleness |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Valentin Kavalenka | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Driver Changes: | Not Needed |
| Description |
Summary
MotivationWho is the affected end user?Any spec reader. How does this affect the end user?The current description confuses readers. Here is a thread started by john.page@mongodb.com as a result of the current description: https://mongodb.slack.com/archives/C0UDE2DL6/p1692201093620479. How likely is it that this problem or use case will occur?I am guessing, that it is not likely, as I don't think many people read this spec. If the problem does occur, what are the consequences and how severe are they?Someone will be confused again, maybe will have to spend time thinking about it or asking questions. Is this issue urgent?Not urgent, no deadline. Is this ticket required by a downstream team?No. Is this ticket only for tests?This improvement affects neither implementations, nor tests. Acceptance CriteriaThe descriptions of lastWrite.lastWriteDate/opTime are clear and correct, and if possible, don't look alien when compared with the descriptions in the official docs. |
| Comments |
| Comment by Tom Selander [ 22/Aug/23 ] |
|
Triage: Good idea to clarify but not urgent and our current quarter is full. Backlogging |