[
https://issues.apache.org/jira/browse/BEAM-7064?focusedWorklogId=226838&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-226838
]
ASF GitHub Bot logged work on BEAM-7064:
----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Apr/19 18:31
Start Date: 12/Apr/19 18:31
Worklog Time Spent: 10m
Work Description: amaliujia commented on issue #8289: [BEAM-7064] Reject
BigQuery data with sub-millisecond precision, instead of losing data
URL: https://github.com/apache/beam/pull/8289#issuecomment-482677983
Run SQL PostCommit
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 226838)
Time Spent: 50m (was: 40m)
> 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: Critical
> Time Spent: 50m
> 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
(v7.6.3#76005)
