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 2021/02/26 17:19:03 UTC

[jira] [Commented] (BEAM-11692) Support DataflowRunner as an underlying runner of InteractiveRunner

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

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

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.

> Support DataflowRunner as an underlying runner of InteractiveRunner
> -------------------------------------------------------------------
>
>                 Key: BEAM-11692
>                 URL: https://issues.apache.org/jira/browse/BEAM-11692
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-py-interactive
>            Reporter: Ning Kang
>            Assignee: Ning Kang
>            Priority: P2
>              Labels: stale-assigned
>
> When using DataflowRunner as an underlying runner and GCS buckets as cache dirs, the `ib.show()` and `ib.collect()` misbehaves because the cache manager does not wait for cache file to be written while DataflowRunner running on Dataflow service takes a long time to complete the write tasks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)