knockknock10 commented on issue #34419: URL: https://github.com/apache/beam/issues/34419#issuecomment-6824594605
Hi @scwhittle, If u don't mind 🙂 I'd be interested in helping investigate this issue. I went through the discussion around exception propagation at fused DoFn boundaries. The case that particularly concerns me is when the upstream DoFn catches an exception thrown by the downstream DoFn, making the bundle appear to have continued successfully even though downstream processing failed. I'd like to start with a focused Java harness regression test for a fused A → B pipeline where B throws and A has its own exception handling. From there, I'd be interested in exploring how the exception can be recorded at the consumer boundary and surfaced as a bundle failure without allowing subsequent outputs to continue incorrectly. Is this still part of the Beam 3.0 plan, and would a test-first contribution be useful at this stage? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
