Suppose we have an aggregate pipeline consisting of two $lookups, the first of which targets a ‘from’ collection that is neither sharded nor a view, but the second of which is a view (or sharded). Currently, when the AutoGet for multiple collections is acquired, the fact that one of the secondary namespaces is sharded/a view will inhibit the pushdown of any $lookup stages in the front of the pipeline that target regular collections . This ticket tracks the work to relax this restriction so that any $lookup stage in the front of the pipeline can be pushed down, even if later $lookup stages target views or sharded collections.