You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/04/08 17:20:00 UTC

[jira] [Commented] (BEAM-11940) JsonToRow can catch errors in downstream transforms

    [ https://issues.apache.org/jira/browse/BEAM-11940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317360#comment-17317360 ] 

Beam JIRA Bot commented on BEAM-11940:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> JsonToRow can catch errors in downstream transforms
> ---------------------------------------------------
>
>                 Key: BEAM-11940
>                 URL: https://issues.apache.org/jira/browse/BEAM-11940
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>    Affects Versions: 2.26.0, 2.27.0, 2.28.0
>            Reporter: Reza ardeshir rokni
>            Assignee: Reza ardeshir rokni
>            Priority: P3
>              Labels: stale-assigned
>
> JsonToRow :
>  
> |try {|
> | | |
> | |output.get(PARSED_LINE).output(jsonToRow(objectMapper(), element));|
> | | |
> | |} catch (Exception ex) {|
> Can catch errors thrown downstream with runners that have fusion. This can be confusing as it can appear that the issue happens in the parse operation , when its really happening in a transform further down the DAG. This is made worse as different runners can show different behaviour in this situation.
>  
> Replace with try\{i = parse}catch{}  if i not null output



--
This message was sent by Atlassian Jira
(v8.3.4#803005)