Hi Greg,
I’ve found the problem’s cause. In fact you spotted a really mean and
subtle bug introduced by FLINK-3327. In a nutshell, the problem is that we
now send the ExecutionConfig as part of the JobGraph to the JobManager. The
ExecutionConfig can contain classes (Class) of automatically
registe
I realized shortly after responding that since I had moved the offending
code into Gelly, which jar I then copied into the lib folder, that this
would not be interfacing the user classloader. So I have merged the Gelly
jar as well as the Gelly examples jar into a single jar which is included
in my
Hi Till,
The code in question is part of FLINK-2909 which is currently running on
Travis but which does not trigger this issue. I'll keep looking.
Thanks,
Greg
On Tue, Mar 15, 2016 at 11:30 AM, Till Rohrmann
wrote:
> Hi Greg,
>
> could you share an example program with us which reproduces the
Hi Greg,
could you share an example program with us which reproduces the problem? I
suspect that, somehow, your user code class BlockInfo is sent directly to
the JobManager where it is deserialized without the user code class loader.
Cheers,
Till
On Tue, Mar 15, 2016 at 4:19 PM, Greg Hogan wr
