[
https://issues.apache.org/jira/browse/BEAM-8442?focusedWorklogId=341394&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-341394
]
ASF GitHub Bot logged work on BEAM-8442:
----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Nov/19 17:57
Start Date: 11/Nov/19 17:57
Worklog Time Spent: 10m
Work Description: robertwb commented on issue #10004: [BEAM-8442] Unify
bundle register in Python SDK harness
URL: https://github.com/apache/beam/pull/10004#issuecomment-552547680
The control plane is asynchronous, but still ordered. IIRC bundle
registration was synchronous before such that if a bundle was not registered,
an error could be thrown rather than waiting around for a registration that may
never come. What is the behavior after this CL if the registration does not
complete before the process bundle instruction is seen?
----------------------------------------------------------------
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: 341394)
Time Spent: 4h 40m (was: 4.5h)
> Unify bundle register in Python SDK harness
> -------------------------------------------
>
> Key: BEAM-8442
> URL: https://issues.apache.org/jira/browse/BEAM-8442
> Project: Beam
> Issue Type: Sub-task
> Components: sdk-py-harness
> Reporter: sunjincheng
> Assignee: sunjincheng
> Priority: Major
> Fix For: 2.18.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> There are two methods for bundle register in Python SDK harness:
> `SdkHarness._request_register` and `SdkWorker.register.` It should be unfied.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
