-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Aggregation Framework
-
Minor Change
-
ALL
-
v4.0
-
Query 2018-09-24
Currently, if a stage (e.g. `$lookup`) has a "sub" pipeline that requires it to write persistent data, the stage's diskRequirement doesn't reflect that.
Instead the parent stage should have the max diskRequirement of it's pipeline's stages under the total ordering
kNoDiskUse < kWritesTmpData < kWritesPersistentData
e.g. of the bug https://github.com/mongodb/mongo/blob/b93fe0e61bf7e8bc96da2edeb66afa1b915b0b77/src/mongo/db/pipeline/document_source_lookup.h#L100-L112
- has to be done after
-
SERVER-34902 view definitions should *not* allow $out as a stage
- Closed
- related to
-
SERVER-36185 Allow specifying bypassDocumentValidation for each $out in an aggregation pipeline
- Backlog
-
SERVER-37140 Investigate what other StageConstraints are "inheritable"
- Closed