Hi Tim, Yes, there is already an email thread and an open Jira (AVRO-2328) about this topic. Feel free to comment on the design doc or Jira if you have any thoughts to share.
Thanks, Nandor On Wed, May 8, 2019 at 11:30 PM Tim Swast <[email protected]> wrote: > Oops, just saw > http://mail-archives.apache.org/mod_mbox/avro-dev/201905.mbox/browser, > I'll > follow that thread for more info about this. > > * • **Tim Swast* > * • *Software Friendliness Engineer > * • *Google Cloud Developer Relations > * • *Seattle, WA, USA > > > *From: *Tim Swast <[email protected]> > *Date: *Wed, May 8, 2019 at 2:26 PM > *To: * <[email protected]> > > I do not see a type for representing naive / civil time / explicitly no > > timezone timestamps in Avro files. > > > > BigQuery has this functionality through the DATETIME data type. > Currently, > > when BigQuery exports to Avro, they encode the value as an RFC 3339 > string, > > but without timezone information (e.g. "1970-01-01T00:00:00") and call > the > > logical type / SQL type "datetime", but this behavior isn't currently > > documented. > > > > I'd like for BigQuery to use a community standard for datetime > > (timezoneless timestamps), so it'd be great to get some consensus on how > it > > should do this. > > > > Related work: Parquet uses timestamp logical type, but with > > "isAdjustedToUTC" parameter for this use case > > https://issues.apache.org/jira/browse/PARQUET-1545 > > >
