[
https://issues.apache.org/jira/browse/BEAM-8402?focusedWorklogId=376940&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-376940
]
ASF GitHub Bot logged work on BEAM-8402:
----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Jan/20 17:39
Start Date: 24/Jan/20 17:39
Worklog Time Spent: 10m
Work Description: boyuanzz commented on issue #9811: [BEAM-8402] Create a
class hierarchy to represent environments
URL: https://github.com/apache/beam/pull/9811#issuecomment-578228342
> Thank you @chadrik. Option 2 sounds good and I can work with TFX team to
update their code.
>
> @udim This I believe came as a breaking change in 2.18 and we might want
to add a note to the release notes about this. (Even add a note on 2.19 since
that will also have the breaking change. @boyuanzz)
Ack. Thanks for handling this!
----------------------------------------------------------------
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: 376940)
Time Spent: 5h 40m (was: 5.5h)
> 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: 5h 40m
> 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)
