The newly introduced AutoGetCollectionForReadLockFreePITCatalog utility first snapshots the CollectionPtr object from the StorEx catalog and then attaches it a description. This is incorrect, because while the StorEx catalog can read at a point-in-time, the Sharding one cannot and always returns "latest". Because of this it is possible that an older collection content can be wrongly paired with a newer description, thus rendering the shard key application nonsensical.

Until CSS::getCollectionDescription is made timestamp-aware, a check needs to be performed based on the UUID of the collection to ensure that the two can be paired and SnapshotTooOld exception should be thrown.

Note that in practice, this is not possible to hit, because the Router Role is not going to find a history across drop/recreate so any queries will fail there.