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 Wed, 24 Aug 2016 01:01:21 GMT


ASF GitHub Bot commented on BEAM-261:

GitHub user tweise reopened 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 05d0762b01ca3003e74d5f87ec85098e3bfb8542
Author: Thomas Weise <>
Date:   2016-06-27T18:24:13Z

    BEAM-261 Apex runner PoC

commit a5a864251589ae875f2f7223abda10c306c35d1d
Author: Thomas Weise <>
Date:   2016-08-16T23:59:15Z

    Merge branch 'master' into BEAM-261

commit d54970963e782fd86482e9407d4ad9aa636562bc
Author: Thomas Weise <>
Date:   2016-08-17T00:07:16Z

    update version

commit 75db3a4161a353cd39b7ee1630a90f5e4fa2186e
Author: Thomas Weise <>
Date:   2016-08-18T04:22:42Z

    BEAM-261 Rebase Apex runner and fix dependency analyze issue.

commit 2a754060aa7e6507047d51aacf087ceaa3544fa7
Author: Thomas Weise <>
Date:   2016-08-18T21:41:24Z

    Shutdown embedded cluster after results are in.

commit aa5640faf1217be016a568687d80049a9e380c0f
Author: Thomas Weise <>
Date:   2016-08-19T15:51:31Z

    Changes for debugging CI issue, to be truncated.

commit 49940c29da00dc6a01d51e222be0e4dcac95a1f6
Author: Thomas Weise <>
Date:   2016-08-19T15:55:42Z

    skip all other tests

commit 1ef679856741c343f526c287968e34cf09a772fe
Author: Thomas Weise <>
Date:   2016-08-19T16:52:09Z

    really add netlet tests

commit 31a0a3cad668f42232c018d5502d35a7d2505fce
Author: Vlad Rozov <>
Date:   2016-08-19T22:47:53Z

    check for localhost

commit 57267c94e540aeb74a273ef1b7d66164c7070a59
Author: Vlad Rozov <>
Date:   2016-08-19T23:08:57Z

    check for localhost

commit 3b6379f680dedce4553d94109396807ef6a0ed29
Author: Vlad Rozov <>
Date:   2016-08-19T23:23:35Z

    check for localhost

commit c6a8b2a7a3de37681412596b5ecd70e7e91f59b9
Author: Vlad Rozov <>
Date:   2016-08-20T01:23:30Z

    check for localhost

commit 6eca03bf117b4112f3e4719cf081d5d5c8385994
Author: Thomas Weise <>
Date:   2016-08-23T21:47:34Z

    Add another test to check address resolution.


> 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