[jira] [Updated] (BEAM-6762) Behavior requires documentation: Pipeline can't run before fusion

["Kenneth Knowles (Jira)" <ji...@apache.org>]

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

Kenneth Knowles updated BEAM-6762:
----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> Behavior requires documentation: Pipeline can't run before fusion
> -----------------------------------------------------------------
>
>                 Key: BEAM-6762
>                 URL: https://issues.apache.org/jira/browse/BEAM-6762
>             Project: Beam
>          Issue Type: Task
>          Components: runner-core
>            Reporter: Kyle Weaver
>            Priority: P3
>              Labels: documentation
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When I was prototyping a portable runner, I tested using a trivial pipeline:
> {noformat}
> PCollection<byte[]> result = pipeline.apply("impulse", Impulse.create());
> PAssert.thatSingleton(result).isEqualTo(new byte[]{});
> {noformat}
> When I tried traversing this pipeline, I found that the URN for the transform PAssert$0 was strangely missing. Turns out GreedyPipelineFuser solves this problem. I don't know why this is so, but I think this behavior should at least be documented in the [runner authoring guide|https://beam.apache.org/contribute/runner-guide/#pipeline] to save future runner authors some debugging.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)