[jira] [Updated] (BEAM-11940) JsonToRow try{}catch{} around output can cause confusing behaviour

["Brian Hulette (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-11940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Hulette updated BEAM-11940:
---------------------------------
    Affects Version/s: 2.27.0
                       2.28.0

> JsonToRow try{}catch{} around output can cause confusing behaviour
> ------------------------------------------------------------------
>
>                 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
>
> 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)