[
https://issues.apache.org/jira/browse/FLINK-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636537#comment-14636537
]
ASF GitHub Bot commented on FLINK-1927:
---------------------------------------
GitHub user zentol opened a pull request:
https://github.com/apache/flink/pull/931
[FLINK-1927][py] Operator distribution rework
Python operators are no longer serialized and shipped across the
cluster. Instead the plan file is executed on each node, followed by
usage of the respective operator object.
removed dill library
also fixed [FLINK-2173] by always passing file paths explicitly to python
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zentol/flink python_operator4
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/931.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 #931
----
commit 40fd3501cacb7b382c7265f0370d0f94887b7e85
Author: zentol <[email protected]>
Date: 2015-07-21T19:22:19Z
[FLINK-1927][py] Operator distribution rework
Python operators are no longer serialized and shipped across the
cluster. Instead the plan file is executed on each node, followed by
usage of the respective operator object.
removed dill library
[FLINK-2173] filepaths are always explicitly passed to python
----
> [Py] Rework operator distribution
> ---------------------------------
>
> Key: FLINK-1927
> URL: https://issues.apache.org/jira/browse/FLINK-1927
> Project: Flink
> Issue Type: Improvement
> Components: Python API
> Affects Versions: 0.9
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Minor
> Fix For: 0.9
>
>
> Currently, the python operator is created when execution the python plan
> file, serialized using dill and saved as a byte[] in the java function. It is
> then deserialized at runtime on each node.
> The current implementation is fairly hacky, and imposes certain limitations
> that make it hard to work with. Chaining, or generally saving other
> user-code, always requires a separate deserialization step after
> deserializing the operator.
> These issues can be easily circumvented by rebuilding the (python) plan on
> each node, instead of serializing the operator. The plan creation is
> deterministic, and every operator is uniquely identified by an ID that is
> already known to the java function.
> This change will allow us to easily support custom serializers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
