[GitHub] beam pull request #3295: [BEAM-593] Refactor Flink execution as preparation ...

[aljoscha <gi...@git.apache.org>]

GitHub user aljoscha opened a pull request:

    https://github.com/apache/beam/pull/3295

    [BEAM-593] Refactor Flink execution as preparation for async job control

    This is just the basic refactoring extracted from #2915. I think we should get this in rather quickly because several people seem to be working on Flink Runner stuff.
    
    @peihe You might like to take a look, among other things I ported your recent additions on `FlinkPipelineExecutionEnvironment` (which doesn't exist anymore now) to the new `FlinkStreamingPipelineExecutor`.

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

    $ git pull https://github.com/aljoscha/beam jira-593-flink-executor-refactoring

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

    https://github.com/apache/beam/pull/3295.patch

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

    This closes #3295
    
----
commit ff2f12e5cca349c0fb8f89d74333284828639721
Author: Aljoscha Krettek <al...@gmail.com>
Date:   2017-05-05T12:13:01Z

    Add FlinkPipelineExecutor with subclasses for batch and streaming
    
    This replaces the old FlinkPipelineExecutionEnvironment which was
    responsible for both batch and stream execution, which made the code
    more complicated.

commit 151f05373c3926f349093232a682a022ba1153bd
Author: Aljoscha Krettek <al...@gmail.com>
Date:   2017-06-05T11:17:51Z

    Replace Flink PipelineTranslationOptimizer by internal method

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---