[
https://issues.apache.org/jira/browse/FLINK-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401765#comment-15401765
]
ASF GitHub Bot commented on FLINK-4265:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2294
@greghogan I am not sure I completely understand this. If I see it
correctly, the no-op operator is in the API, but gets removed during the
translation?
It looks like a bit of a hacky approach to me. Can you try and explain how
exactly it helps?
> Add a NoOpOperator
> ------------------
>
> Key: FLINK-4265
> URL: https://issues.apache.org/jira/browse/FLINK-4265
> Project: Flink
> Issue Type: New Feature
> Components: DataSet API
> Affects Versions: 1.1.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
> Priority: Minor
> Fix For: 1.1.0
>
>
> One recent feature of Gelly is algorithms which detect duplicated or similar
> computation which can be shared. My initial implementation could only reuse a
> {{DataSet}} result. Before committing to Flink this was updated to use a
> javassist {{ProxyFactory}} allowing configuration to be merged and results to
> be replaced. There were some issues, as identified in FLINK-4257. With a
> {{NoOpOperator}} we can remove the use of {{ProxyFactory}} and resolve the
> identified issues.
> This ticket adds a {{NoOpOperator}} which is unwound in
> {{OperatorTranslation.translate}}. The {{NoOpOperator}} contains a
> {{DataSet}} which is accessed by a getter and setter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
