[jira] [Work logged] (BEAM-8402) Create a class hierarchy to represent environments

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-8402?focusedWorklogId=339098&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-339098 ]

ASF GitHub Bot logged work on BEAM-8402:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Nov/19 00:44
            Start Date: 06/Nov/19 00:44
    Worklog Time Spent: 10m 
      Work Description: robertwb commented on issue #9811: [BEAM-8402] Create a class hierarchy to represent environments
URL: https://github.com/apache/beam/pull/9811#issuecomment-550089460
 
 
   Yes, this is mostly about the public API. This does create a module of environments, with several pre-defined, which gets us a step closer to just using these in the public API, which is not I think a scalable/portable way forward. We should at least add a caveat to that module that these are intended for internal use only. 
 
----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 339098)
    Time Spent: 2h  (was: 1h 50m)

> 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: 2h
>  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)