[
https://issues.apache.org/jira/browse/BEAM-9051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015243#comment-17015243
]
Ryan Berti commented on BEAM-9051:
----------------------------------
Looks like AvroUtils.toBeamRowStrict can replace BigQueryUtils.toBeamRow in our
use case. I'm going to close this ticket and BEAM-9052. Sounds like the Avro
support in BigQueryUtils should be deprecated.
> 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
> 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)
