You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/01/20 18:44:39 UTC
[jira] [Commented] (FLINK-3135) Add chainable driver for
UNARY_NO_OP strategy
[ https://issues.apache.org/jira/browse/FLINK-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109019#comment-15109019 ]
ASF GitHub Bot commented on FLINK-3135:
---------------------------------------
GitHub user ramkrish86 opened a pull request:
https://github.com/apache/flink/pull/1530
FLINK-3135 Add chainable driver for UNARY_NO_OP strategy(Ram)
My first flink PR. A simple way to add a Chainable Driver for UNARY_NO_OP. Just followed the existing code pieces and also reading the NoOpDriver created the NoOpChainedDriver. Just trying to learn and happy to work on feedbacks/comments.
Since here the input just needs to be passed to the output there is no need for any class to be loaded I felt. Hence most of the abstract APIs have empty implementations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ramkrish86/flink FLINK-3135
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1530.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 #1530
----
commit 16b755a78e2cd56e193363dc3cd77d87eeaa7a16
Author: ramkrishna <ra...@gmail.com>
Date: 2016-01-20T17:22:55Z
FLINK-3135 Add chainable driver for UNARY_NO_OP strategy(Ram)
----
> Add chainable driver for UNARY_NO_OP strategy
> ---------------------------------------------
>
> Key: FLINK-3135
> URL: https://issues.apache.org/jira/browse/FLINK-3135
> Project: Flink
> Issue Type: Improvement
> Components: Local Runtime
> Affects Versions: 1.0.0
> Reporter: Fabian Hueske
> Priority: Minor
> Labels: starter
>
> A chainable driver for UNARY_NO_OP strategy would decrease the serialization overhead in certain situations.
> Should be fairly easy to implement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)