We store row identifiers in a SET table to process batch updates to a MergeTree table. Typical query would look like:

ALTER TABLE large_table DELETE WHERE id IN target_set

If the table target_set is dropped before the mutation is completed, the mutation is toast (latest_fail_reason : target_set not available (or something to that effect)

I was expecting that the information required to perform the DELETE statement was captured at query time.