You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Anonymous (Jira)" <ji...@apache.org> on 2023/04/13 11:01:00 UTC
[jira] [Updated] (BEAM-8402) Create a class hierarchy to represent environments
[ https://issues.apache.org/jira/browse/BEAM-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anonymous updated BEAM-8402:
----------------------------
Status: Triage Needed (was: Resolved)
> 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: P2
> Labels: backward-incompatible
> Fix For: 2.18.0
>
> Time Spent: 5h 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.20.10#820010)