[
https://issues.apache.org/jira/browse/BEAM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082486#comment-16082486
]
Kenneth Knowles commented on BEAM-2583:
---------------------------------------
Is it a bug to catch an exception and continue to use the pipeline? I would say
that is a completely normal thing to do, unless we explicitly document against
it. And even docs are a thin excuse - hence I think we should make the Pipeline
forcibly unusable.
> 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)
