[
https://issues.apache.org/jira/browse/BEAM-4244?focusedWorklogId=721442&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-721442
]
ASF GitHub Bot logged work on BEAM-4244:
----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Feb/22 12:40
Start Date: 05/Feb/22 12:40
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on pull request #15344:
URL: https://github.com/apache/beam/pull/15344#issuecomment-1030616272
This pull request has been marked as stale due to 60 days of inactivity. It
will be closed in 1 week if no further activity occurs. If you think that’s
incorrect or this pull request requires a review, please simply write any
comment. If closed, you can revive the PR at any time and @mention a reviewer
or discuss it on the [email protected] list. Thank you for your
contributions.
--
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]
Issue Time Tracking
-------------------
Worklog Id: (was: 721442)
Time Spent: 50m (was: 40m)
> 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: 50m
> 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)
