[
https://issues.apache.org/jira/browse/BEAM-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131804#comment-17131804
]
Beam JIRA Bot commented on BEAM-3337:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Create an Executable Graph representation in the Universal Local Runner
> -----------------------------------------------------------------------
>
> Key: BEAM-3337
> URL: https://issues.apache.org/jira/browse/BEAM-3337
> Project: Beam
> Issue Type: Bug
> Components: runner-core
> Reporter: Thomas Groh
> Priority: P2
> Labels: portability, stale-P2
>
> This represents the entirety of a Pipeline, divided into executable stages
> which are executed in either the runner or within a user container. This
> representation must include the ports over which the SDK harness communicates
> to the runner.
> The construction of this graph likely includes most of the nodes present
> within the Runner API graph (PTransform and PCollection), but injects
> additional nodes to represent a remote read or write between harnesses.
> Simple fusion (naive producer/consumer and sibling fusion) also should be
> performed here.
> This will also require rewriting some boundary coders (e.g. runner -> SDK
> Harness and vice versa) to be agnostic to the language of the runner harness,
> likely by converting into length-prefixed bytes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
