dropIndexes events do not have total ordering in change streams

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: 6.0.16, 7.0.10, 8.0.0-rc4
    • Component/s: None
    • None
    • Query Execution
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The dropIndex command generates an oplog entry on every shard containing the sharded collection. When clusterTime on 2 or more shards is identical, the corresponding change stream events will be indistiguishable including the resume token.

      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:
            4 Start watching this issue

              Created:
              Updated: