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

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

                Author: ASF GitHub Bot
            Created on: 13/Oct/20 01:30
            Start Date: 13/Oct/20 01:30
    Worklog Time Spent: 10m 
      Work Description: KevinGG commented on a change in pull request #13080:
URL: https://github.com/apache/beam/pull/13080#discussion_r503617113



##########
File path: sdks/python/apache_beam/runners/interactive/background_caching_job.py
##########
@@ -19,21 +19,21 @@
 
 For internal use only; no backwards-compatibility guarantees.
 
-A background caching job is a job that captures events for all capturable
+A background caching job is a job that records events for all recordable

Review comment:
       Switched to background source recording jobs for all the comments.




----------------------------------------------------------------
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: 499757)
    Time Spent: 1h 20m  (was: 1h 10m)

> Fix warning message and rename old APIs
> ---------------------------------------
>
>                 Key: BEAM-11056
>                 URL: https://issues.apache.org/jira/browse/BEAM-11056
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-py-interactive
>            Reporter: Ning Kang
>            Assignee: Ning Kang
>            Priority: P2
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> When invoking `ib.evict_captured_data()`, the logging contains a typo 
> `recordeddata`:
> `You have requested Interactive Beam to evict all recordeddata that could be 
> deterministically replayed among multiple pipeline runs.`
> Also, the `capture_control` should be renamed to `record_control`. All 
> occurrences of `capture` should be changed to `record` to keep the 
> consistency of large source recording improvements.



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

Reply via email to