Great, thanks for reporting back!
2018-01-09 18:05 GMT+01:00 ani.desh1512 :
> Hi Fabian,
> Thanks a lot for the reply. Setting the classloader.resolve-order
> configuration seems to have done the trick. For anybody else, having the
> same problem as this, this is the config that I set:
>
> /*clas
Hi Fabian,
Thanks a lot for the reply. Setting the classloader.resolve-order
configuration seems to have done the trick. For anybody else, having the
same problem as this, this is the config that I set:
/*classloader.resolve-order: parent-first
classloader.parent-first-patterns:
java.;org.apache.f
Hi Aniket,
you could try to restore the previous behavior by configuring
classloader.resolve-order: parent-first
in the Flink configuration.
Best, Fabian
2018-01-08 23:09 GMT+01:00 ani.desh1512 :
> *Background:* We have a setup of Flink 1.3.2 along with a secure MAPR
> (v5.2.1) cluster (Flink
*Background:* We have a setup of Flink 1.3.2 along with a secure MAPR
(v5.2.1) cluster (Flink is running on mapr client nodes). We run this flink
cluster via flink-jobmanager.sh foreground and flink-taskmanager.sh
foreground command via Marathon. We want to upgrade to Flink 1.4.0.
Since, we requir
