You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/03/11 00:40:00 UTC
[jira] [Updated] (BEAM-14091) Fixing Interactive Beam show/collect for remote runners
[ https://issues.apache.org/jira/browse/BEAM-14091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-14091:
-----------------------------------
Status: Open (was: Triage Needed)
> Fixing Interactive Beam show/collect for remote runners
> -------------------------------------------------------
>
> Key: BEAM-14091
> URL: https://issues.apache.org/jira/browse/BEAM-14091
> Project: Beam
> Issue Type: Bug
> Components: runner-py-interactive
> Reporter: Victor Chen
> Assignee: Victor Chen
> Priority: P2
>
> * Bug: the show and collect commands under Interactive Beam would eventually call a PipelineFragment to execute the InteractiveRunner corresponding to the given PCollection. The PipelineFragment by default does not wait for pipeline to finish execution, and when a pipeline runs remotely, the Interactive Environment is not updated with the results of the pipeline run. Subsequent calls to ib.show/ib.collect would rerun the pipeline instead of directly retrieving the results from the Interactive Environment.
> * Setting the blocking to always be True inside the RecordingManager.record() method when calling the .run() method of the PipelineFragment properly saves completed pipeline results in the Interactive Environment and prevents a need to rerun the pipelines again on subsequent calls to ib.show/ib.collect.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)