Jeremiah Jordan

Thinking about this some more, I am worried some about this immediately breaking a bunch of users workloads without any warning. I wonder if we should track the primary key...

> Alternatively, we might consider documenting (in release notes or upgrade guidelines) that if it's a non-backward compatible change the value of the batch guardrail should be adjusted accordingly. Nobody...

was this missed? should it be rebased and merged?

Don't know about the removal, but the fix lgtm.