You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2022/05/20 17:00:00 UTC

[jira] [Commented] (BEAM-14331) Make InteractiveRunner work without runner api roundtrip

    [ https://issues.apache.org/jira/browse/BEAM-14331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540213#comment-17540213 ] 

Beam JIRA Bot commented on BEAM-14331:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> Make InteractiveRunner work without runner api roundtrip
> --------------------------------------------------------
>
>                 Key: BEAM-14331
>                 URL: https://issues.apache.org/jira/browse/BEAM-14331
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-py-interactive
>            Reporter: Ning
>            Assignee: Ning
>            Priority: P2
>              Labels: stale-assigned
>
> InteractiveRunner still uses a runner api roundtrip to make "deep copies" of pipelines.
> Such a roundtrip is not guaranteed to work especially when a transform is not serializable. Example issues is BEAM-14112.
>  
> Though a temporary fix could be made, a better approach is to refactor the implementation of InteractiveRunner to always work on runner api protos without relying on roundtrip or "deep copies".



--
This message was sent by Atlassian Jira
(v8.20.7#820007)