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

Investigate reverting to simpler token version transition mechanism

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution

      In SERVER-81295, we introduced a more stringent mechanism for handling the transition between token versions. This was motivated by the fact that v2 has a new "split fragment" feature that v1 cannot produce, and so resuming from a v1 token could, in certain cases, prevent an event at the same clusterTime from being split. It was also necessary because both v1 and v2 tokens have an eventIdentifier field, but its format differs between v1 and v2 even for the same event.

      In the future, particularly once v1 is no longer generated by supported versions, it may be desirable to revert to the simpler transition mechanism when moving between different token versions.

            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            bernard.gorman@mongodb.com Bernard Gorman
            0 Vote for this issue
            2 Start watching this issue