You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2014/11/12 21:01:35 UTC
[jira] [Commented] (FLINK-1238) Add a way to deactivate the
"mutable object safe mode"
[ https://issues.apache.org/jira/browse/FLINK-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208586#comment-14208586 ]
Fabian Hueske commented on FLINK-1238:
--------------------------------------
+1 that would be very good!
> Add a way to deactivate the "mutable object safe mode"
> ------------------------------------------------------
>
> Key: FLINK-1238
> URL: https://issues.apache.org/jira/browse/FLINK-1238
> Project: Flink
> Issue Type: Bug
> Components: Local Runtime
> Affects Versions: 0.8-incubating
> Reporter: Stephan Ewen
> Priority: Minor
> Fix For: 0.8-incubating
>
>
> Currently, the runtime operators for Join and Cross operate in a safe mode concerning objects:
> Whenever a cross or join function is called with the same object more than once (for cross always, for join in all but the 1:1 join cases), the runtime makes deep copies of the objects before calling the join function.
> Even if the join function modifies the objects that were given into the function, the next call to the function will pass the original unmodified value. It is a safe mode for programmers that operate more in a Hadoop-ish way, were it was very common to modify the objects rather than creating new ones.
> I would add an option to disable that mode, as it does cost performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)