Add change stream unwinding tests for writes during primary-driven index build

XMLWordPrintableJSON

    • Type: Engineering Test
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Storage Execution 2026-06-22, Storage Execution 2026-07-06
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Change streams must unwind kApplyOpsAppliedAtomically applyOps entries into individual operation events, not transaction events. Container side write operations (ci/cu/cd on admin.$container) must be filtered out and never emitted as change stream events. Verify that exactly 3 user events (insert, update, delete) are emitted, that none carry lsid/txnNumber, and that resume tokens work across the boundary.

            Assignee:
            Shin Yee Tan
            Reporter:
            Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: