Culby4335 opened a new issue, #34465: URL: https://github.com/apache/beam/issues/34465
### What would you like to happen? The ability to capture the messages that fail being written to kafka because of transient errors would be nice that way we have a way of checking if the message did make it to our final destination. Right now we just assume it makes it but it would be great to capture these errors in a result to use to write to an error table that we can then check later. The main error we are seeing is failure to connect to the Kafka ad server, we know with streaming it will auto retry but in batch we are kind of blind on what failed and what passed, but the functionality should be there for both. ### Issue Priority Priority: 2 (default / most feature requests should be filed as P2) ### Issue Components - [x] Component: Python SDK - [x] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [x] Component: IO connector - [ ] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- 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: github-unsubscr...@beam.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
