You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Tyson Hamilton (Jira)" <ji...@apache.org> on 2020/09/09 16:05:00 UTC

[jira] [Commented] (BEAM-1110) Propagate operator- and pipeline-level metadata where possible

    [ https://issues.apache.org/jira/browse/BEAM-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193005#comment-17193005 ] 

Tyson Hamilton commented on BEAM-1110:
--------------------------------------

Apex runner has been removed.

> Propagate operator- and pipeline-level metadata where possible
> --------------------------------------------------------------
>
>                 Key: BEAM-1110
>                 URL: https://issues.apache.org/jira/browse/BEAM-1110
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-apex
>            Reporter: Dan Halperin
>            Priority: P3
>
> User metadata from Beam pipelines:
> * Aggregators (/ Metrics)
> * Step names
> * Pipeline options
> It would be nice to propagate these metadata to the REST APIs served by the stram. From talking to [~sandeepdeshmukh], this seems doable but probably not done yet.
> Supporting these features will give Beam pipelines a consistent experience across runners. See also this [blog post|https://cloud.google.com/blog/big-data/2016/06/dataflow-updates-see-more-details-about-your-pipelines] for how this is realized in the Cloud Dataflow runner, and a related JIRA (BEAM-1107) for the Flink Runner.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)