[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:
Related
is related to SERVER-35419 Make diskRequirement in StageConstrai... Closed
Assigned Teams:
Query Optimization
Participants:

 Description   

Consider an aggregation pipeline that uses $lookup to write to multiple namespaces via $out:

db.coll0.aggregate([
    {$lookup: {from: "coll1", pipeline: [{$out: "coll2"}], as: "empty"}},
    {$lookup: {from: "coll3", pipeline: [{$out: "coll4"}], as: "empty"}}
], {bypassDocumentValidation: true});

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 SERVER-35419 has some related discussion.

Comment by Ian Whalen (Inactive) [ 20/Jul/18 ]

charlie.swanson to find the related ticket and link it here.

Generated at Thu Feb 08 04:42:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.