-
Type: Bug
-
Resolution: Cannot Reproduce
-
Priority: Major - P3
-
None
-
Affects Version/s: 6.0.4
-
Component/s: None
-
Query Execution
-
ALL
-
-
QE 2023-09-18, QE 2023-10-02, QE 2023-10-16, QE 2023-10-30, QE 2023-11-13, QE 2023-11-27
Change Stream: Shard keys are captured in documentKey on delete operations performed when connected to mongos and mongodb+srv, but not directly to MongoDB instances.
Perform the following operations listed in the Steps To Reproduce section while reading from ChangeStream.
It can be seen that shard keys and their values are captured by the change stream when the delete operations were performed by mongosh connections that were connected to mongos or mongodb+srv (Cases 1 & 2), but not by connections that were directly connected to the MongoDB database instances (Case 3). This behavior is exhibited only for delete operations. It was noted that update change events had shard keys in their document keys in all these scenarios.
- related to
-
SERVER-75993 Change Streams: Document key is not fully captured
- Backlog