In SERVER-83839 it was found that when we have a pipeline with a large number of match expressions, and pipeline optimization disabled, as well as the query knob introduced in that ticket enabled (so we don't have Filter -> Sargable node rewrites) this results in a memory error during optimization because we generate one FilterNode per DocumentSourceMatch (when pipeline opt is off, we don't merge the stages).

This should not be a bug in practice, since we run with optimization enabled outside of testing environments; however, this could turn out to be an issue during fuzzer testing. Furthermore, the optimizer probably should not be reliant on pipeline optimization occurring in order to obtain correct results.

Furtehrmore, if some other mechanism for generating a large number of filter nodes exists, this would actually be an issue.