drill-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristine Hahn <kh...@maprtech.com>
Subject Re: Understanding Drill's timestamp and timezone
Date Tue, 12 May 2015 16:53:40 GMT
Thanks, yes it is confusing. There's some documentation  on
http://drill.apache.org/docs/data-type-conversion/#time-zone-limitation
about the limitation and conversion functions, but there's lots of room for
improvement.

Kristine Hahn
Sr. Technical Writer
415-497-8107 @krishahn


On Mon, May 11, 2015 at 10:13 PM, Adam Gilmore <dragoncurve@gmail.com>
wrote:

> I must say - this is really confusing and seems to be undocumented.
>
> I think if Drill is going to not support a timestamp with timezone in the
> near future, it should deal with ALL date/times as UTC, or at the very
> least provide functions to convert between the two where applicable.
>
> For example, the new extended JSON support ($date) will parse a date such
> as "2015-01-01T00:22:00Z" and convert it to the local time.  So if you were
> to (as we are) create a Parquet table from JSON (with extended JSON), then
> all the dates in the Parquet file will be created as local time
> (incorrectly).
>
> On Fri, May 8, 2015 at 12:14 PM, Hao Zhu <hzhu@maprtech.com> wrote:
>
> > Hi Team,
> >
> > Recently spent some time to test the Drill's timestamp behavior, so
> sharing
> > the article "Understanding Drill's timestamp and timezone
> > <http://www.openkb.info/2015/05/understanding-drills-timestamp-and.html
> >".
> >
> > This article tests the behaviors under different Drill's timezones and
> > source data's timezones.
> >
> > Thanks,
> > Hao
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message