Sorry for the delay, been on holidays. I think I can make the new behaviour opt-in by adding a new method to the builder, similar to what I did in #5341.
I'm not sure though on what to do about your second comment. Maybe just limiting to batch jobs? (using `expandUntriggered`?) although I think having the job result information is really valuable in all cases, even if it changes the record granularity. [ Full content available at: https://github.com/apache/beam/pull/6055 ] This message was relayed via gitbox.apache.org for [email protected]
