[
https://issues.apache.org/jira/browse/BEAM-4145?focusedWorklogId=112963&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-112963
]
ASF GitHub Bot logged work on BEAM-4145:
----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Jun/18 00:35
Start Date: 19/Jun/18 00:35
Worklog Time Spent: 10m
Work Description: jkff opened a new pull request #5680: [BEAM-4145]
Populate the worker_id metadata in the Java SDK Harness
URL: https://github.com/apache/beam/pull/5680
This is a take-over of #5456 since Thomas is currently unavailable.
I took the PR verbatim, rebased it / resolved conflicts, and addressed the
review comments:
- Added a comment about lifetime of logging service.
- To "We are loosing the original list of interceptors here." - I think it's
conventional to have a withFoo(List) method overwrite the list rather than
append, so no action on this one.
R: @angoenka
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 112963)
Time Spent: 3h 40m (was: 3.5h)
> Java SDK Harness populates control request headers with worker id
> -----------------------------------------------------------------
>
> Key: BEAM-4145
> URL: https://issues.apache.org/jira/browse/BEAM-4145
> Project: Beam
> Issue Type: New Feature
> Components: sdk-java-harness
> Reporter: Ben Sidhom
> Assignee: Eugene Kirpichov
> Priority: Minor
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Runner code needs to be able to identify incoming harness connections by the
> worker ids that it assigns to them on creation. This is currently done by the
> go boot code when the harness runs in a docker container. However, in-process
> harnesses never specify worker ids. This prevents in-process harnesses from
> being multiplexed by a runner (most likely the ULR and test code).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
