Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-30800

'invalidate' changeStream entries should always have a null _id

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Repl 2017-09-11

      Since it's not valid to resume after an 'invalidate' change stream entry, those entries shouldn't return a ResumeToken at all. Instead their _id should always be an explicit null so it's clear that it's not safe to resume after them.

            Assignee:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: