[SERVER-69652] Investigate improved rewrites based on knowledge of the change stream spec Created: 13/Sep/22 Updated: 05/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Bernard Gorman | 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 |
|
It may be possible to improve rewrites based on examination of the supplied change streams spec, or to introduce new rewrites. For instance, if the fullDocument parameter is default, we know that update events will never have a fullDocument field. Since the change stream spec is now available on the ExpressionContext, it is already accessible to all rewrites and does not require any new plubming. |