MongoDB 3.6下C#驱动Change Stream仅收更新通知，如何设置OperationType？

Hey there, let's figure out why your MongoDB 3.6 change stream is only picking up update events but missing inserts. I've worked through similar issues with Change Streams before, so here are the key areas to check:

1. Double-Check Your Change Stream Filter #

Even if you thought you used the "default" setup, it's easy to accidentally add a filter that excludes insert events. For example, in C# code, if you explicitly added a $match stage that only targets Update operations, inserts will be ignored entirely.

Verify your pipeline doesn't have something like this:

// ❌ This will ONLY listen for updates
var badPipeline = new EmptyPipelineDefinition<ChangeStreamDocument<BsonDocument>>()
    .Match(change => change.OperationType == ChangeStreamOperationType.Update);

Instead, to listen for both inserts and updates, either use an unfiltered pipeline (which listens for all operation types by default) or explicitly include both:

// ✅ Listens for inserts AND updates
var goodPipeline = new EmptyPipelineDefinition<ChangeStreamDocument<BsonDocument>>()
    .Match(change => 
        change.OperationType == ChangeStreamOperationType.Insert || 
        change.OperationType == ChangeStreamOperationType.Update);

2. Confirm Your Deployment Architecture #

MongoDB 3.6 Change Streams only work with replica sets or sharded clusters—they are not supported on standalone instances. If you're running a single-node MongoDB server, you might see inconsistent behavior (like partial event delivery) instead of a clear error.

Double-check your deployment: run rs.status() in the mongo shell. If it returns an error about not being in a replica set, that's your problem. You'll need to convert your instance to a single-node replica set to use Change Streams properly.

3. Timing Matters: Start the Stream Before Inserting #

Change Streams only capture events that occur after the stream is initialized. If you inserted documents before starting your Change Stream listener, those inserts won't show up. Make sure your code starts the stream first, then performs the insert operations you want to monitor.

4. Verify Driver Version Compatibility #

Ensure you're using a MongoDB C# driver version that fully supports MongoDB 3.6 Change Streams. The minimum compatible driver version is 2.7.x—older versions might have bugs or incomplete support for insert events in Change Streams.

You can check your driver version via NuGet, or in code:

Console.WriteLine($"MongoDB Driver Version: {MongoDB.Driver.MongoDBVersion.Version}");

5. Check Permissions and Logs #

• Permissions: Make sure the database user your application uses has the changeStream privilege on the target database/collection. Without this, the stream might not be able to capture all event types.
• MongoDB Logs: Look through your mongod logs for any errors or warnings related to Change Streams. Search for keywords like changeStream or oplog—this can reveal issues like oplog truncation (which would lose insert events) or permission failures.

Bonus: Compare with the MongoDB Test Code #

You mentioned looking at the C# driver's test code, which uses insert-then-update flows and captures both events. Compare your setup to those tests:

• Are they using a replica set? (Almost certainly yes)
• Do they use the same driver version as you?
• Is their pipeline configuration identical to yours?

Often, aligning your environment and code with the test cases will resolve the discrepancy.

内容的提问来源于stack exchange，提问作者Michael Westberg