I was able to replicate the exact problem and error message using Joda time.
On Fri, Apr 1, 2016 at 1:06 PM, Ted Dunning <[email protected]> wrote: > > OK. I have run a few tests and the time you mention is, indeed, a moment > that doesn't strictly speaking exist due to the daylight savings transition. > > In my experiments, however, I find that Java's utilities in java.util such > as GregorianCalendar and SimpleDateFormat all seem to treat 2:34 on the > morning in question as a synonym for 3:34. > > Apparently the Drill code is doing something else, possible using Joda > time. > > > > On Fri, Apr 1, 2016 at 9:29 AM, Ted Dunning <[email protected]> wrote: > >> >> Was this a day that daylight savings turned on? That would mean that time >> went from 1:59 to 3:00. The implication would be that there was no legal >> time 2:34:20. >> >> How do you think this should be handled? >> >> Sent from my iPhone >> >> > On Apr 1, 2016, at 6:54, John Omernik <[email protected]> wrote: >> > >> > SYSTEM ERROR: IllegalInstantException: Cannot parse "2003-04-06 >> 02:34:20": >> > Illegal instant due to time zone offset transition (America/Chicago) >> > Fragment 3:9 >> > >> > Looking at that date, it doesn't look like an illegal moment in time, >> it's >> > not near a leap year or anything funny like that. >> > >
