[
https://issues.apache.org/jira/browse/BEAM-8402?focusedWorklogId=332249&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-332249
]
ASF GitHub Bot logged work on BEAM-8402:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Oct/19 21:42
Start Date: 22/Oct/19 21:42
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-545168831
> I think Robert's idea is to specify a set of required runtime
dependencies, in the form of "Java with Beam 2.16.0 with libraries XY"; and
then let Beam create an environment that fits these requirements.
That's how I was reading it as well. While that's potentially more user
friendly, it also seems quite challenging. If I request "Java with Beam
2.16.0", and the runner happens to be using Java, it seems unsafe to assume
that an embedded process is a valid replacement for docker, not in the least
because I may have my own custom docker container for Beam-Java. That said,
it's still a very interesting idea. Is there a ticket for this idea yet?
Since that idea seems like it could take awhile to be designed and executed,
I'm hoping that we can move forward with this PR in the meantime. I think
that the progress that we make on this and the subsequent work on the semantics
of assigning environments to transforms (possibly including
[BEAM-7850](https://issues.apache.org/jira/browse/BEAM-7850)), would be useful
in any case. Any hey, we can always mark it as experimental :)
----------------------------------------------------------------
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: 332249)
Time Spent: 1h 10m (was: 1h)
> 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: 1h 10m
> 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)
