You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:50:04 UTC
[jira] [Updated] (BEAM-4244) Provide a better way for programmatically handling errors raised while encoding/decoding data
[ https://issues.apache.org/jira/browse/BEAM-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-4244:
----------------------------------
This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.
> Provide a better way for programmatically handling errors raised while encoding/decoding data
> ---------------------------------------------------------------------------------------------
>
> Key: BEAM-4244
> URL: https://issues.apache.org/jira/browse/BEAM-4244
> Project: Beam
> Issue Type: New Feature
> Components: beam-model, runner-core
> Reporter: Chamikara Madhusanka Jayalath
> Priority: P3
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Beam runners use coders in various stages of a pipeline to encode/decode data. Coders are executed directly by the runner of a pipeline and user do not have control over exceptions raised during encoding/decoding (could be either due to malformed/corrupted data provided by users or intermediate malformed/corrupted data generated during the system execution).
> Currently users can rely on runner-specific worker logging to detect the error and update the pipeline but it would be better if we can provide a way to programmatically handle these errors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)