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

Make consistent notifyChangeStreams API

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Execution

    Description

      After PM-1950, there are an increasing number of places where we write a no-op oplog message to signify to change streams that a particular event has occurred. Most of these places are now named notifyChangeStreamsOn* but are scattered throughout the code. We should make sure that ALL such no-op writers are named notifyChangeStreamsOn (e.g. the shardCollection no-op writer is currently just called _writeOplogMessage, the reshardBegin and reshardDoneCatchUp events are not in separate functions at all) and consolidate these into a dedicated library and API.

      Attachments

        Activity

          People

            sebastien.mendez@mongodb.com Sebastien Mendez
            bernard.gorman@mongodb.com Bernard Gorman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: