[
https://issues.apache.org/jira/browse/BEAM-6762?focusedWorklogId=209154&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-209154
]
ASF GitHub Bot logged work on BEAM-6762:
----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Mar/19 21:08
Start Date: 06/Mar/19 21:08
Worklog Time Spent: 10m
Work Description: ibzib commented on issue #7992: [BEAM-6762] Add Javadoc
mentioning pipeline fusion
URL: https://github.com/apache/beam/pull/7992#issuecomment-470277240
> PortablePipelineRunner is used in sdk for submitting the pipeline and does
not have any control over what happens on the JobServer.
PortablePipelineRunner is running within the JobServer. (I added this
interface in the `runners/fnexecution/jobsubmission` directory to go with
JobInvoker and JobInvocation)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 209154)
Time Spent: 0.5h (was: 20m)
> 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: Minor
> Labels: documentation
> Time Spent: 0.5h
> 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
(v7.6.3#76005)
