beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-147) Introduce an easy API pipeline metrics
Date Thu, 29 Sep 2016 00:04:21 GMT


ASF GitHub Bot commented on BEAM-147:

GitHub user bjchambers opened a pull request:

    [BEAM-147] Prototype of Metrics API for Java DirectRunner

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [*] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [*] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [*] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [*] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

You can merge this pull request into a Git repository by running:

    $ git pull metrics

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1024
commit 40961aa24468c810f5f3377620fe14bc7d40c55c
Author: bchambers <>
Date:   2016-09-20T19:44:39Z

    Initial prototype of Beam Metrics API
    This is labeled @Experimental since it is only supported by the Direct
    Runner and may change as it is implemented in other runners.
    Future work includes adding additional kinds of metrics and wiring them
    up to the various runners.

commit 0c73cf2f2fb73eb1d171c911c10b36f79d564899
Author: bchambers <>
Date:   2016-09-27T23:41:10Z

    squash! Prototype Distribution metrics


> Introduce an easy API pipeline metrics
> --------------------------------------
>                 Key: BEAM-147
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: beam-model, sdk-java-core, sdk-py
>            Reporter: Robert Bradshaw
>            Assignee: Ben Chambers
> The existing Aggregators are confusing both because of their name and because they serve
multiple purposes.
> Previous discussions around Aggregators/metrics/etc.
> See discussion at
and . Exact
name still being bikeshedded.

This message was sent by Atlassian JIRA

View raw message