Yes, that worked, I restarted my drill cluster using -Duser.timezone=UTC on startup. Per the other thread that I found after the fact (I was traveling) this works, but I wonder if we can't have a less intrusive fix. I.e. restarting the drill cluster to fix this (by adding the system property) is a pretty far reaching fix, and could have other downstream affects. I see how this can come up, I just wonder if there could be some sort of option (using alter session), which per the other thread didn't appear to be the case, that we could use. Changing the Drill bit time zone affects all users, alter session would be more localized (and if we had this, we should update the error message to possibly suggest the DST thing, with the proper command.
Could we as a long term fix try to add a synonym for the time? I think that's the proper way to handle things as the time truly doesn't exist, so instead of just throwing an error add an hour and call it good. :) On Fri, Apr 1, 2016 at 3:32 PM, Ted Dunning <[email protected]> wrote: > On Fri, Apr 1, 2016 at 6:54 AM, 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 > > > > > Can you set your timezone to +0600 to avoid DST transitions? Will that > break things? >
