You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2015/09/15 08:42:45 UTC
[jira] [Closed] (FLINK-2669) Execution contains non-serializable
field
[ https://issues.apache.org/jira/browse/FLINK-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ufuk Celebi closed FLINK-2669.
------------------------------
Resolution: Won't Fix
Yeah, I agree and I didn't mean to "fix" this (that's also why I've labelled it as minor). I saw that request job is just used for the memory archivist. And it was actually not what I needed. I know that there is nothing we can do about it at this point.
> Execution contains non-serializable field
> -----------------------------------------
>
> Key: FLINK-2669
> URL: https://issues.apache.org/jira/browse/FLINK-2669
> Project: Flink
> Issue Type: Bug
> Components: Distributed Runtime
> Affects Versions: master, 0.9.1
> Reporter: Ufuk Celebi
> Priority: Minor
>
> Execution is {{Serializable}}, but non-transient field {{assignedResource}} of type {{SimpleSlot}} is not.
> I've noticed this while sending a {{JobManagerMessages.RequestJob}} to a job manager, which returns the {{ExecutionGraph}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)