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

Consider hashing eventIdentifier in resume token

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Execution

    Description

      The eventIdentifier field in a change stream resume token is currently encoded as the raw documentKey or operationDescription of the associated event. It is therefore of indeterminate size, and since resume tokens are repeated several times in a batch of results (_id, sort key, postBatchResumeToken) this places some constraints on the maximum size of an event.

      For the telemetry and query settings projects, we have opted to encode query shape as a SHA-256 hash, considering this sufficient to avoid collisions. We should consider doing the same for eventIdentifier.

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            bernard.gorman@mongodb.com Bernard Gorman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: