[
https://issues.apache.org/jira/browse/BEAM-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252968#comment-17252968
]
Chamikara Madhusanka Jayalath commented on BEAM-4244:
-----------------------------------------------------
I'll be OOO for few weeks but please note that JIRAs have very low visibility
so I suggest mentioning your issues in the dev list to get ideas from other
devs. Also Jira is currently not used as a way to prioritize work. It's just a
tracking tool.
Additionally, new contributions/ideas to Beam are always welcome. So if you
have any proposals in this space, please mention that in the dev list as well.
> 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
>
> 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.3.4#803005)
