Make sure events with large documentKey do not crash change stream

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Query Execution
    • None
    • Query Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      For change events with fullDocument field, the documentKey would be duplicated in the fullDocument field. If the document has large documentKey, the total size of the event would exceed the 16MB bson limit because of the duplication, and cause the change stream cursor to fail. What could be worse is that the resumeToken can also encode documentKey, resulting in more duplicates. We need to investigate approaches to mitigate this.

            Assignee:
            [DO NOT USE] Backlog - Query Execution
            Reporter:
            Wenbin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: