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

["Kenneth Knowles (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-1110:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> 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)