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/03/05 17:19:02 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=17296210#comment-17296210 ] 

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

This issue was marked "stale-assigned" and has not received a public comment in 7 days. It is now automatically unassigned. If you are still working on it, you can assign it to yourself again. Please also give an update about the status of the work.

> 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
>            Priority: P2
>
> 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)