[
https://issues.apache.org/jira/browse/BEAM-7064?focusedWorklogId=227865&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-227865
]
ASF GitHub Bot logged work on BEAM-7064:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Apr/19 17:56
Start Date: 15/Apr/19 17:56
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-483354915
With a flag, which behavior should be the default?
Aggressive plan is to fail users pipelines so make exception approach as the
default.
Or we can be more cautious to allow truncating timestamp by default.
It's more like a short term pain (possibly breaking change to some users) vs
long term pain (transparent precision truncation that is hard to detect for
both existing and new users).
----------------------------------------------------------------
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: 227865)
Time Spent: 2h 50m (was: 2h 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: 2h 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)
