[SERVER-78768] Consider adding nss to endOfTransaction event depending on the change stream type Created: 07/Jul/23 Updated: 08/Jul/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ivan Fefer | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
Rather than omitting the ns entirely, or trying to list every affected namespace, it might be preferable to have the ChangeStreamEventTransformation synthesize a namespace for the EOT based on the stream type. A single-coll stream would have ns: {db: db, coll: coll}. {}A database stream would have ns: {db: db} {}A whole-cluster stream would have ns: {db: admin}. {}The latter two potentially also including coll: "$cmd". |