Allow specifying bypassDocumentValidation for each $out in an aggregation pipeline

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.6.0
    • Component/s: Aggregation Framework
    • None
    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Query Optimization
            Reporter:
            Kyle Suarez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: