Re: Class loading and job versioning

2016-07-20 Thread Michal Budzyn
ould be way too high. Best, Max On Wed, Jul 20, 2016 at 2:23 PM, Michal Budzyn mailto:michal.budzyn.ext...@zalando.de>> wrote: > Thanks for the prompt replay. > > You are right. The conflict was between "com.fasterxml.jackson.core" libs.

Re: Class loading and job versioning

2016-07-20 Thread Michal Budzyn
ould be way too high. Best, Max On Wed, Jul 20, 2016 at 2:23 PM, Michal Budzyn mailto:michal.budzyn.ext...@zalando.de>> wrote: > Thanks for the prompt replay. > > You are right. The conflict was between "com.fasterxml.jackson.core" libs.

Re: Class loading and job versioning

2016-07-20 Thread Michal Budzyn
tch 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 Bud

Class loading and job versioning

2016-07-20 Thread Michal Budzyn
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