Clarify behaviour when picking up checkpoint without metadata or ID configured

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Checkpoints
    • Storage Engines, Storage Engines - Foundations
    • SE Foundations - Q3+ Backlog
    • None

      When picking up new checkpoints, we expect either checkpoint.checkpoint_meta or checkpoint.checkpoint_id to be set. Currently, if neither are set, we pick a special "none" value and roll with that. But this behaviour should be better specified – ideally, MongoDB should always be able to specify a checkpoint ID, so perhaps we should fail if one is not provided.

              Assignee:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              Will Korteland
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: