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

Always include the collection UUID in the change stream resumeToken

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • QE 2022-04-04, QE 2022-04-18

      The collection UUID field is ordered before the 'eventIdentifier', so if we want to log the 'eventIdentifier', we also needed the UUID to be present. For certain operations, like dropDatabase or events on view, the UUID is absent. We should use a null value for these cases.

            Assignee:
            mickey.winters@mongodb.com Mickey Winters
            Reporter:
            arun.banala@mongodb.com Arun Banala
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: