[
https://issues.apache.org/jira/browse/BEAM-2085?focusedWorklogId=585469&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-585469
]
ASF GitHub Bot logged work on BEAM-2085:
----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Apr/21 23:38
Start Date: 19/Apr/21 23:38
Worklog Time Spent: 10m
Work Description: tvalentyn commented on a change in pull request #14390:
URL: https://github.com/apache/beam/pull/14390#discussion_r616242588
##########
File path: sdks/python/apache_beam/runners/pipeline_context.py
##########
@@ -118,13 +120,19 @@ def get_by_id(self, id):
def get_by_proto(self, maybe_new_proto, label=None, deduplicate=False):
# type: (message.Message, Optional[str], bool) -> str
+ obj = self._obj_type.from_runner_api(
Review comment:
I wanted to reference the commmit in this PR that isolates this
particular change. But thanks for adding the reference to the PR that seems to
introduce the bug.
I think the current approach in component id map assumes that we maintain
`id->proto`
and (bidirectional) `id<->obj` relations. Whenever one of `(obj, proto)` is
added to context, the counterpart is obtained through translation. Then
inverse `proto->id` relation is currently not maintained in a map. But it is
computed via `proto->FromRunnerAPI->obj->id` lookup. I suppose we could add a
map to cache this lookup? But I think this does not change the assumption that
both obj, and proto are needed to add a new element to the map.
--
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: 585469)
Time Spent: 23h 20m (was: 23h 10m)
> Transforms could give hints to runners on resource requirements
> ---------------------------------------------------------------
>
> Key: BEAM-2085
> URL: https://issues.apache.org/jira/browse/BEAM-2085
> Project: Beam
> Issue Type: Improvement
> Components: beam-model, runner-core, sdk-java-core
> Affects Versions: Not applicable
> Reporter: Ismaël Mejía
> Assignee: Valentyn Tymofieiev
> Priority: P3
> Labels: Clarified
> Time Spent: 23h 20m
> Remaining Estimate: 0h
>
> As discussed in BEAM-673 runners can allocate workers to accomplish their
> work in a better way if they can take into account some hints from the
> transforms, e.g. a source can hint data locality and with this information
> the runner can allocate the workers in an better way, this can also be the
> case with a particular transform that can suggest to the runner to be
> executed in a worker with a specific resource, e.g. GPU.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
