[SERVER-31416] Ban $changeStream stage in $lookup pipeline Created: 05/Oct/17 Updated: 30/Oct/23 Resolved: 10/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Bernard Gorman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2017-10-23 |
| Participants: |
| Description |
|
The $changeStream stage should not be allowed inside a $lookup pipeline, since there is no way to get "all" results from a tailable cursor. Also, while we do not currently allow the user to specify a pipeline for $graphLookup, and $changeStream is banned in views, we should look ahead to ensuring $changeStream is not allowed in a $graphLookup pipeline if we allow users to specify $graphLookup pipelines in the future. |
| Comments |
| Comment by Githook User [ 10/Oct/17 ] |
|
Author: {'email': 'bernard.gorman@gmail.com', 'name': 'Bernard Gorman', 'username': 'gormanb'}Message: |