----------------------------

Original Description

Description:

In 3.6, a change stream could be opened on a non-existent collection in a replica set or sharded cluster, but only if the database already existed. After this commit, a stream can be opened on a non-existent collection before the enclosing database has been created.

Engineering Ticket Description:

Opening a change stream against a non-existent db/collection in a single replica set works fine, however the same test in a sharded cluster fails with "InvalidNamespace".

----------------------------

Description

Scope of changes (files that need work and how much)

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)