[
https://issues.apache.org/jira/browse/BEAM-8335?focusedWorklogId=389625&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-389625
]
ASF GitHub Bot logged work on BEAM-8335:
----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Feb/20 21:12
Start Date: 19/Feb/20 21:12
Worklog Time Spent: 10m
Work Description: aaltay commented on pull request #10899: [BEAM-8335]
Background Caching job
URL: https://github.com/apache/beam/pull/10899#discussion_r381537314
##########
File path:
sdks/python/apache_beam/runners/interactive/background_caching_job.py
##########
@@ -19,29 +19,113 @@
For internal use only; no backwards-compatibility guarantees.
-A background caching job is a job that caches events for all unbounded sources
-of a given pipeline. With Interactive Beam, one such job is started when a
-pipeline run happens (which produces a main job in contrast to the background
+A background caching job is a job that captures events for all capturable
+sources of a given pipeline. With Interactive Beam, one such job is started
when
+a pipeline run happens (which produces a main job in contrast to the background
caching job) and meets the following conditions:
- #. The pipeline contains unbounded sources.
+ #. The pipeline contains capturable sources, configured through
+ interactive_beam.options.capturable_sources.
#. No such background job is running.
#. No such background job has completed successfully and the cached events
are
- still valid (invalidated when unbounded sources change in the pipeline).
+ still valid (invalidated when capturable sources change in the pipeline).
Once started, the background caching job runs asynchronously until it hits some
-cache size limit. Meanwhile, the main job and future main jobs from the
pipeline
-will run using the deterministic replay-able cached events until they are
-invalidated.
+capture limit configured in interactive_beam.options. Meanwhile, the main job
+and future main jobs from the pipeline will run using the deterministic
+replayable captured events until they are invalidated.
"""
# pytype: skip-file
from __future__ import absolute_import
+import logging
+import threading
+import time
+
import apache_beam as beam
-from apache_beam import runners
from apache_beam.runners.interactive import interactive_environment as ie
+from apache_beam.runners.interactive.caching import streaming_cache
+from apache_beam.runners.runner import PipelineState
+
+_LOGGER = logging.getLogger(__name__)
+_LOGGER.setLevel(logging.INFO)
Review comment:
Is this needed? This will override otherthings.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 389625)
Time Spent: 62h 20m (was: 62h 10m)
> Add streaming support to Interactive Beam
> -----------------------------------------
>
> Key: BEAM-8335
> URL: https://issues.apache.org/jira/browse/BEAM-8335
> Project: Beam
> Issue Type: Improvement
> Components: runner-py-interactive
> Reporter: Sam Rohde
> Assignee: Sam Rohde
> Priority: Major
> Time Spent: 62h 20m
> Remaining Estimate: 0h
>
> This issue tracks the work items to introduce streaming support to the
> Interactive Beam experience. This will allow users to:
> * Write and run a streaming job in IPython
> * Automatically cache records from unbounded sources
> * Add a replay experience that replays all cached records to simulate the
> original pipeline execution
> * Add controls to play/pause/stop/step individual elements from the cached
> records
> * Add ability to inspect/visualize unbounded PCollections
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
