[ 
https://issues.apache.org/jira/browse/BEAM-10603?focusedWorklogId=485951&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-485951
 ]

ASF GitHub Bot logged work on BEAM-10603:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Sep/20 20:32
            Start Date: 17/Sep/20 20:32
    Worklog Time Spent: 10m 
      Work Description: rohdesamuel commented on pull request #12799:
URL: https://github.com/apache/beam/pull/12799#issuecomment-694484142


   > > The failing test seems to be a related test in Windows: 
https://github.com/apache/beam/pull/12799/checks?check_run_id=1119719710
   > > Can you check whether it's related to this PR (and fix if so), and if 
not still try to send in a fix in a new PR?
   > 
   > Fixed it! The InteractiveEnvironment was being recreated for every test 
which works if everything is in serial. But the tests are run in parallel so 
tests were destroying each other's environments.
   
   Brian pinged me on the flaky tests so I moved it out of this PR and into 
https://github.com/apache/beam/pull/12866


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 485951)
    Time Spent: 34h 10m  (was: 34h)

> Large Source Recording for Interarctive Runner
> ----------------------------------------------
>
>                 Key: BEAM-10603
>                 URL: https://issues.apache.org/jira/browse/BEAM-10603
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-py-interactive
>            Reporter: Sam Rohde
>            Assignee: Sam Rohde
>            Priority: P1
>          Time Spent: 34h 10m
>  Remaining Estimate: 0h
>
> This changes the Interactive Runner to create a long-running background 
> caching job that is decoupled from the user pipeline. When a user invokes a 
> collect() or show(), it will read from the cache to compute the requested 
> PCollections. Previously, the user would have to wait for the cache to be 
> fully written to. This allows for the user to start experimenting immediately.



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

Reply via email to