You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Brian Hulette (Jira)" <ji...@apache.org> on 2021/03/29 16:30:00 UTC

[jira] [Updated] (BEAM-7064) Conversion of timestamp from BigQuery row to Beam row loses precision

     [ https://issues.apache.org/jira/browse/BEAM-7064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Hulette updated BEAM-7064:
--------------------------------
    Fix Version/s: 2.13.0
         Assignee: Kenneth Knowles
       Resolution: Fixed
           Status: Resolved  (was: Open)

Yep looks like this was resolved in pr/8289. Thanks!

> 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)