flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Budzyn <michal.budzyn.ext...@zalando.de>
Subject Re: Class loading and job versioning
Date Wed, 20 Jul 2016 12:23:49 GMT
Thanks for the prompt replay.

You are right. The conflict was between "com.fasterxml.jackson.core" libs.

I am just wondering. If the the jobs were separted from the platform,

the jobs libs should have precedence and no versioning problem should 
have happened.

Regards,

Michal


On 20.07.2016 14:00, Maximilian Michels wrote:
> Hi Michal,
>
> I couldn't find Joda in flink-dist. Possibly there is some other clash?
>
> There are two potential issues here:
>
> 1) Flink shades some libraries (Guava) but not all. If you use a
> version of a library in your Flink job which doesn't match the one in
> flink-dist, you're bound for trouble.
>
> 2) Flink separates jobs from each other to avoid potential class
> version mismatches. Each job has its own classloader. In this sense,
> "job versioning" is supported.
>
> Cheers,
> Max
>
> On Wed, Jul 20, 2016 at 1:02 PM, Michal Budzyn
> <michal.budzyn.extern@zalando.de> wrote:
>> Hi all,
>> We had a class versioning problem within Flink Job.
>> The job uses Joda 2.6, but the flink-dist 1.0.3 packages 2.5.
>> The problem was solved by relocating job classes with shade plug-in.
>>
>> Does flink separate jobs from each other to avoid class conflicts between
>> them and the platform ?
>> Is job versioning supported or is shading always required ?
>>
>> Regards,
>> Michal
>>


Mime
View raw message