You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ryan Berti (Jira)" <ji...@apache.org> on 2020/01/14 17:49:00 UTC
[jira] [Resolved] (BEAM-9051) BigQueryUtils toBeamRow to support
GenericRecords with millisecond precision timestamps
[ https://issues.apache.org/jira/browse/BEAM-9051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Berti resolved BEAM-9051.
------------------------------
Fix Version/s: Not applicable
Resolution: Won't Fix
> BigQueryUtils toBeamRow to support GenericRecords with millisecond precision timestamps
> ---------------------------------------------------------------------------------------
>
> Key: BEAM-9051
> URL: https://issues.apache.org/jira/browse/BEAM-9051
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Affects Versions: 2.16.0
> Reporter: Ryan Berti
> Assignee: Ryan Berti
> Priority: Minor
> Fix For: Not applicable
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Currently, BigQueryUtils assumes all Avro GenericRecords which utilize timestamp fields include timestamp data in microseconds when converting from GenericRecords to Beam Rows ([https://github.com/apache/beam/blob/master/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryUtils.java#L568]). The implementation should also support timestamp data in milliseconds; this should be feasible by referencing the LogicalType associated with the avro field to determine if the underlying value is represented in millis or micros.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)