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 2021/01/26 22:43:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Kenneth Knowles updated BEAM-11692:
-----------------------------------
    Status: Open  (was: Triage Needed)

> 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
>
> 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)