You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@drill.apache.org by Julian Hyde <jh...@apache.org> on 2017/02/10 18:49:51 UTC

Time zone

Can someone please clarify the timezone behavior of Drill’s TIMESTAMP data type. According to the SQL standard, there is no timezone stored in a TIMESTAMP value, nor is there an implicit time zone (such as UTC or the server or session’s time zone).

Under the standard model, TIMESTAMP ‘2017-02-10 10:46:00’ does not represent ‘2017-02-10 10:46:00 PST’ or ‘2017-02-10 10:46:00 UTC’ or ‘2017-02-10 18:46:00 UTC’, nor does it represent a particular instant in time. It just represents a clock on the wall reading ‘2017-02-10 10:46:00’.

I was under the impression that Drill implements standard behavior, but https://drill.apache.org/docs/data-type-conversion/#time-zone-limitation <https://drill.apache.org/docs/data-type-conversion/#time-zone-limitation> and http://www.openkb.info/2015/05/understanding-drills-timestamp-and.html#.VUzhotpVhHw <http://www.openkb.info/2015/05/understanding-drills-timestamp-and.html#.VUzhotpVhHw> make me doubt.

Julian