Feature Description
When using Online DDL w/--in-order-completion, it's possible for a migration to appear to "never cut over", because it is waiting for another migration to complete first
As a user of Online DDL, I would like to understand what a migration using --in-order-completion is waiting on
Use Case(s)
Online DDL w/--in-order-completion feature enabled