Rename collection events do not have total ordering in change streams

XMLWordPrintableJSON

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

      The renameCollection command in v6.0 generates a change event per shard. These events may get identical resume tokens.

      This does not make any problems when change stream events are consumed contiguously, however, if the stream is interrupted and resumed on the first of the identical events, the subsequent identical events will be skipped which might be unexpected by some event readers.

            Assignee:
            Unassigned
            Reporter:
            Romans Kasperovics
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: