[
https://issues.apache.org/jira/browse/BEAM-8402?focusedWorklogId=330315&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-330315
]
ASF GitHub Bot logged work on BEAM-8402:
----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Oct/19 06:04
Start Date: 18/Oct/19 06:04
Worklog Time Spent: 10m
Work Description: chadrik commented on issue #9811: [BEAM-8402] Create a
class hierarchy to represent environments
URL: https://github.com/apache/beam/pull/9811#issuecomment-543529375
> FWIW, I think we should re-think how what exactly environments mean. In
particular, things like "in process" vs. "docker" are very runner-dependent,
and I think should be handled as runner-substitutions of well-defined
environments like java-2.16 which will make things a lot cleaner in the face of
multi-language pipelines.
Can you explain this a bit more?
In your opinion, do you think that this re-thinking of environments should
precede this PR? The primary problem I see with that is that Viola and I don't
have well-formed opinions on that topic, and making it a prerequisite for this
would hold it up and the subsequent features we'd like to add. My hope is that
we can agree on 2 things:
1) that assigning an environment to parts of a pipeline is something that
should be possible
2) that the general pattern of the `to_runner_api` / `from_runner_api`
protocol for marshaling types between pipeline and portable-runner
representations is viable for environments, and would remain viable through any
future refinement of the standard environments (which I would assume would
happen at the protobuf level and then be propagated out to dependent/adjacent
APIs?)
----------------------------------------------------------------
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: 330315)
Time Spent: 50m (was: 40m)
> Create a class hierarchy to represent environments
> --------------------------------------------------
>
> Key: BEAM-8402
> URL: https://issues.apache.org/jira/browse/BEAM-8402
> Project: Beam
> Issue Type: New Feature
> Components: sdk-py-core
> Reporter: Chad Dombrova
> Assignee: Chad Dombrova
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> As a first step towards making it possible to assign different environments
> to sections of a pipeline, we first need to expose environment classes to the
> pipeline API. Unlike PTransforms, PCollections, Coders, and Windowings,
> environments exists solely in the portability framework as protobuf objects.
> By creating a hierarchy of "native" classes that represent the various
> environment types -- external, docker, process, etc -- users will be able to
> instantiate these and assign them to parts of the pipeline. The assignment
> portion will be covered in a follow-up issue/PR.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
