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

Keystring-encode ResumeTokens to allow bytewise comparisons

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2017-10-02, Repl 2017-10-23
    • 0

      Change notification ResumeTokens are composed of the logical time timestamp, the fully qualified collection name, and the document key of the changed document. In the initial version, these three components will just be fields of a BSON object, and comparisons inside the server for relative ordering will use BSON's woCompare() function. If instead we keystring-encoded that document, then the ResumeTokens become truly opaque blobs which forces users and drivers not to rely on their current format or try to inspect them. It also could give us a performance win since now the internal comparisons the server must do to put notifications in order can be bytewise comparisons instead of needing woCompare().

            Assignee:
            matthew.russotto@mongodb.com Matthew Russotto
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: