[
https://issues.apache.org/jira/browse/BEAM-7064?focusedWorklogId=228003&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-228003
]
ASF GitHub Bot logged work on BEAM-7064:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Apr/19 22:16
Start Date: 15/Apr/19 22:16
Worklog Time Spent: 10m
Work Description: kennknowles 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-483438908
Because of how the TableRow to Beam Row conversion is currently expressed a
bit differently (as a map of typename to parser), it will be a moderate
refactor to share these conversion options. I don't want to confuse this review
with that, but will start work on it since we don't want to lose data there
either.
----------------------------------------------------------------
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: 228003)
Time Spent: 3h 20m (was: 3h 10m)
> 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: 3h 20m
> 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)
