[
https://issues.apache.org/jira/browse/BEAM-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172713#comment-17172713
]
Brian Hulette commented on BEAM-10655:
--------------------------------------
Yeah looks like NanosInstant isn't handled when reading or writing with
BigQueryIO. Since BigQuery's TIMESTAMP type is microsecond precision it could
make sense to also support reading directly to NanosInstant to avoid losing
precision.
The original dev@ thread suggested that the protobuf extensions shouldn't use
NanosInstant and just truncate to Millis/DATETIME, but I think that's a bad
idea. We could provide such an option but I don't think we should do it by
default.
I think it should be possible to workaround this by adding a transform that
converts any NanosInstant fields to DATETIME before the passing to BigQueryIO
> NullPointerException when writing "google.protobuf.Timestamp" to BigQuery
> through schemas
> -----------------------------------------------------------------------------------------
>
> Key: BEAM-10655
> URL: https://issues.apache.org/jira/browse/BEAM-10655
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Reporter: Chamikara Madhusanka Jayalath
> Priority: P2
>
> See here for details and instructions for reproducing.
> [https://lists.apache.org/thread.html/r1657ccf41dda3f2d9d082c5ebb006dd2da92863983971ad23485f16e%40%3Cdev.beam.apache.org%3E]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
