beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bjchambers <>
Subject [GitHub] beam pull request #3053: Metrics to runners core
Date Wed, 10 May 2017 18:44:15 GMT
GitHub user bjchambers opened a pull request:

    Metrics to runners core

    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`.
     - [*] 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-to-runners-core

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 #3053
commit 2bb1ef29fce40dff6d26b6d4dd7ae20ce1ec5c45
Author: bchambers <>
Date:   2017-05-09T22:45:50Z

    [BEAM-2244] Move details of Metrics to Runners Core
    Largeish changes this required were:
      - splitting the MetricsContainer into an interface in Java Core with
        an implementation in Runners Core
      - modifying the various *Cell classes to have a name
      - cleaning up dependency cross-fire.

commit 997440811a4781de2d9489edf50c50ecf9f33536
Author: bchambers <>
Date:   2017-05-10T18:43:43Z

    fixup! Move pieces needed in Dataflow to core-construction-java


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message