There exist processes such as SERVER-120400 where we assume the order of operations however when batching is enabled, the timestamp of an operation is deferred until commit. If there is a set of operations that mixes DDL with non-DDL operations such that the non-DDL operation is intended to have an earlier timestamp, we may see a bug where because it is now batched (and the DDL was not) that the order of these operations change.

We should investigate where else this bug may exist.