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-261) Apache Apex Runner
Date Mon, 27 Jun 2016 18:34:52 GMT


ASF GitHub Bot commented on BEAM-261:

GitHub user tweise opened a pull request:

    [BEAM-261] Apex runner PoC

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [x] 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).
     - [x] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [x] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    R: @kennknowles
    Please note that integration tests are enabled and many are still expected to fail. This
is WIP.

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

    $ git pull BEAM-261

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 #540
commit 3f0de449ea7811eb9020be544a0dec0fa1794f88
Author: Thomas Weise <>
Date:   2016-06-27T18:24:13Z

    BEAM-261 Apex runner PoC


> Apache Apex Runner
> ------------------
>                 Key: BEAM-261
>                 URL:
>             Project: Beam
>          Issue Type: Wish
>          Components: runner-ideas
>            Reporter: Suminda Dharmasena
>            Assignee: Thomas Weise
> Like Spark, Flink and GearPump, Apache Apex also does have advantages. Is it possible
to have a runner for Apache Apex?

This message was sent by Atlassian JIRA

View raw message