[jira] [Commented] (FLINK-1285) Make execution mode configurable

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241380#comment-14241380 ] 

ASF GitHub Bot commented on FLINK-1285:
---------------------------------------

GitHub user aljoscha opened a pull request:

    https://github.com/apache/incubator-flink/pull/259

    [FLINK-1285][FLINK-1137] Make execution mode configurable

    These commits enhance the MutableObjectIterator with a next() method that creates a new object for every call.
    
    The ExecutionEnvironment is updated to have an ExecutionConfig. This allows changing of execution parameters, such as whether the ClosureCleaner should be used and whether objects should be reused.
    
    All Drivers are updated to support both object-reuse mode and non-object-reuse mode. Before, some operators did reuse (map, join...) while some (reduce) had a hidden non-reuse mode. Right now, the reuse mode is set per-job, if necessary, this could also be done on a more fine-grained basis.
    
    Documentation is still missing. I want to do that in a separate commit. Also, I'm waiting for a cluster to run some tests to see what the impact is of using object-reuse vs. non-object-reuse.

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

    $ git pull https://github.com/aljoscha/incubator-flink config-object

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

    https://github.com/apache/incubator-flink/pull/259.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 #259
    
----
commit f149f6403731bd6f60f713c44b8e7952fe5aa2aa
Author: Aljoscha Krettek <al...@gmail.com>
Date:   2014-12-02T16:34:46Z

    [FLINK-1137] Enhance MutableObjectIterator with non-reuse next()
    
    This is in preparation for configurable object-reuse mode. We previously
    referred to this as mutable object vs. mutable object safe mode or some
    such thing.

commit cbfc61a488a412f6587275ff4f4a980a593ce660
Author: Aljoscha Krettek <al...@gmail.com>
Date:   2014-11-26T16:54:37Z

    [FLINK-1285] Make execution mode configurable

commit 5a9634364a46ab3dd8452ebf2858c5896998fa84
Author: Aljoscha Krettek <al...@gmail.com>
Date:   2014-12-05T13:14:25Z

    Enable FastPath in TextValueInputFormat again

----


> Make execution mode configurable
> --------------------------------
>
>                 Key: FLINK-1285
>                 URL: https://issues.apache.org/jira/browse/FLINK-1285
>             Project: Flink
>          Issue Type: Improvement
>          Components: Local Runtime
>            Reporter: Ufuk Celebi
>            Assignee: Aljoscha Krettek
>            Priority: Minor
>
> As discussed in a PR: https://github.com/apache/incubator-flink/pull/227#discussion_r20788430.
> The goal would be to make the execution mode configurable in order to easily configure closure cleaning, custom serializers, object reuse etc.
> Configuration could be done either via 1) setters or 2) a configuration object.
> I vote for 2).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)