[
https://issues.apache.org/jira/browse/BEAM-14091?focusedWorklogId=739793&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-739793
]
ASF GitHub Bot logged work on BEAM-14091:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Mar/22 01:01
Start Date: 11/Mar/22 01:01
Worklog Time Spent: 10m
Work Description: VictorPlusC opened a new pull request #17071:
URL: https://github.com/apache/beam/pull/17071
- 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.
- ASF Jira thread: https://issues.apache.org/jira/browse/BEAM-14091
------------------------
Thank you for your contribution! Follow this checklist to help us
incorporate your contribution quickly and easily:
- [ ] [**Choose
reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and
mention them in a comment (`R: @username`).
- [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA
issue, if applicable. This will automatically link the pull request to the
issue.
- [ ] Update `CHANGES.md` with noteworthy changes.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
See the [Contributor Guide](https://beam.apache.org/contribute) for more
tips on [how to make review process
smoother](https://beam.apache.org/contribute/#make-reviewers-job-easier).
To check the build health, please visit
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
GitHub Actions Tests Status (on master branch)
------------------------------------------------------------------------------------------------
[](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more
information about GitHub Actions CI.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 739793)
Time Spent: 40m (was: 0.5h)
> 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
> Time Spent: 40m
> Remaining Estimate: 0h
>
> * 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)
