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

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

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

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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
>              Labels: stale-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)