Re: Wrong joda lib

2018-05-04 Thread Stefan Richter
Then that is the jar from which it currently takes the code for your DateTime class at that point in the code. > Am 04.05.2018 um 18:29 schrieb Flavio Pompermaier : > > The output of that code is > file:/opt/cloudera/parcels/CDH-5.11.2-1.cdh5.11.2.p0.4/jars/jruby-cloudera-1.0.0.jar > > On Fri,

Re: Wrong joda lib

2018-05-04 Thread Flavio Pompermaier
The output of that code is file:/opt/cloudera/parcels/CDH-5.11.2-1.cdh5.11.2.p0.4/jars/jruby-cloudera-1.0.0.jar On Fri, May 4, 2018 at 6:11 PM, Stefan Richter wrote: > Hi, > > you can try to figure out the jar with org.joda.time.DateTime.class. > getProtectionDomain().getCodeSource().getLocation

Re: Wrong joda lib

2018-05-04 Thread Stefan Richter
Why does it make this a problem? You could also run method in a static block and move the initialization of your variable at the bottom of that static block (or comment it out). > Am 04.05.2018 um 18:14 schrieb Flavio Pompermaier : > > The problem is that the problem occurs during the initiali

Re: Wrong joda lib

2018-05-04 Thread Flavio Pompermaier
The problem is that the problem occurs during the initialization of a static variable: private static final DateTime MIN_DATE = new DateTime(1850, 01, 01, 0, 0); On Fri, May 4, 2018 at 6:11 PM, Stefan Richter wrote: > Hi, > > you can try to figure out the jar with org.joda.time.DateTime.class.g

Re: Wrong joda lib

2018-05-04 Thread Stefan Richter
Hi, you can try to figure out the jar with org.joda.time.DateTime.class.getProtectionDomain().getCodeSource().getLocation() in the right context. Best, Stefan > Am 04.05.2018 um 18:02 schrieb Flavio Pompermaier : > > Hi to all, > I'm trying to run a job on a test cluster with Flink 1.3.1 but