This behavior was introduced in 5.0 due to the fact that DDL implementations on 4.4 and prior versions might leave garbage if the operation doesn't succeed.

However, this is pretty bad for unsharded collections / views: they only live on the primary shard, however we end up targeting all shards.