[
https://issues.apache.org/jira/browse/BEAM-10603?focusedWorklogId=485866&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-485866
]
ASF GitHub Bot logged work on BEAM-10603:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Sep/20 17:21
Start Date: 17/Sep/20 17:21
Worklog Time Spent: 10m
Work Description: TheNeuralBit commented on pull request #12704:
URL: https://github.com/apache/beam/pull/12704#issuecomment-694379028
It looks like this made the windows tests in Python very flaky, I don't
think all three have passed in any runs since (BEAM-10921).
I tested in a rollback (https://github.com/apache/beam/pull/12865) and all
three passed again. I think we should merge that rollback while the flakiness
is debugged, unless there's a clear fix?
----------------------------------------------------------------
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: 485866)
Time Spent: 33h 10m (was: 33h)
> 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: 33h 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)
