ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.1.0-rc1025
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • QE 2026-10-26
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Update code comments to make sure that oplog mayTruncateUpTo is always described as an exclusive upper bound.

      The oplog truncation contract is that at least one record with recordId <= mayTruncateUpTo must remain in the oplog after truncation.

      Also add a short-circuit to skip checking the persisted timestamp when all records are pinned.

            Assignee:
            Anna Veselova
            Reporter:
            Anna Veselova
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: