[SERVER-36185] Allow specifying bypassDocumentValidation for each $out in an aggregation pipeline Created: 18/Jul/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | 3.6.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| Description |
|
Consider an aggregation pipeline that uses $lookup to write to multiple namespaces via $out:
The bypassDocumentValidation specification will apply to all of the target namespaces (coll2 and coll4). If this is a feature we'd like to support, it would be nice to offer the ability to tune the bypassDocumentValidation option on a per-target collection basis. |
| Comments |
| Comment by Charlie Swanson [ 20/Jul/18 ] |
|
I couldn't find a ticket about banning $out inside of a $lookup (which I thought there was one for), but |
| Comment by Ian Whalen (Inactive) [ 20/Jul/18 ] |
|
charlie.swanson to find the related ticket and link it here. |