beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lukecwik <>
Subject [GitHub] beam pull request #1801: Beam Fn API Prototype Implementation
Date Thu, 19 Jan 2017 23:52:09 GMT
GitHub user lukecwik opened a pull request:

    Beam Fn API Prototype Implementation

    An overview is available at
    Code package descriptions:
    org.apache.beam.fn.harness.FnHarness: main entry point
    org.apache.beam.fn.harness.control: Control service client and individual request handlers Data service client and logical stream multiplexing
    org.apache.beam.fn.harness.logging: Logging client implementation and JUL logging handler
adapter gRPC channel management gRPC stream management
    org.apache.beam.fn.harness.fn: Java 8 functional interface extensions
    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`
     - [x] 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 fn_api

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 #1801
commit 4cf07c926865117cffa15beb419e71f9a99237ba
Author: Luke Cwik <>
Date:   2017-01-19T23:16:55Z

    A proposal for a portability framework to execute user definable functions.


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