Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-2694

Clarify lastWrite in the max-staleness spec

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor - P4 Minor - P4
    • None
    • Max Staleness
    • None
    • Not Needed

    Description

      Summary

      Motivation

      Who 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 Criteria

      The 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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            valentin.kovalenko@mongodb.com Valentin Kavalenka
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: