'invalidate' changeStream entries should always have a null _id

XMLWordPrintableJSON

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

      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
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: