beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Groh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2583) Exceptions in expand() corrupt the TransformHierarchy
Date Tue, 11 Jul 2017 16:28:00 GMT

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

Thomas Groh commented on BEAM-2583:
-----------------------------------

Specifically, this only happens if, during a call to {{expand}}, the call throws an exception;
that exception is caught or otherwise handled, and then the user attempts to continue to use
the pipeline. This is very much a bug in the user's code, but it may fail in a non-intuitive
sense (i.e. via NullPointerException)

> Exceptions in expand() corrupt the TransformHierarchy
> -----------------------------------------------------
>
>                 Key: BEAM-2583
>                 URL: https://issues.apache.org/jira/browse/BEAM-2583
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Priority: Minor
>
> Discovered recently during unrelated work that when a composite PTransform (Java) crashes
during expand - for example due to a validation failure - it leaves the Pipeline in a state
that throws NPEs when it is traversed.
> No one has complained, so it doesn't seem critical to fix the mutation logic. But we
should set a bit and poison all future uses of the corrupted pipeline.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message