[
https://issues.apache.org/jira/browse/BEAM-7064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17310824#comment-17310824
]
Kenneth Knowles commented on BEAM-7064:
---------------------------------------
Just to add the most recent update, we have
https://github.com/apache/beam/pull/9849 which adds a pipeline option to
re-enable the truncation. I guess I couldn't decide if "ease of use + loss of
precision" or "harder to use + full precision" was better. So users can choose.
> Conversion of timestamp from BigQuery row to Beam row loses precision
> ---------------------------------------------------------------------
>
> Key: BEAM-7064
> URL: https://issues.apache.org/jira/browse/BEAM-7064
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: P1
> Labels: Clarified
> Fix For: 2.13.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> Currently, the utilities to convert from BigQuery row to Beam row simply
> truncate timestamps at millisecond precision. This is unacceptable. Instead,
> an error should be raised indicating that it is not supported.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
