Kenneth Knowles created BEAM-8456:
-------------------------------------
Summary: BigQuery to Beam SQL timestamp has the wrong default:
truncation makes the most sense
Key: BEAM-8456
URL: https://issues.apache.org/jira/browse/BEAM-8456
Project: Beam
Issue Type: Improvement
Components: dsl-sql
Reporter: Kenneth Knowles
Assignee: Kenneth Knowles
Most of the time, a user reading a timestamp from BigQuery with
higher-than-millisecond precision timestamps may not even realize that the data
source created these high precision timestamps. They are probably timestamps on
log entries generated by a system with higher precision.
If they are using it with Beam SQL, which only supports millisecond precision,
it makes sense to "just work" by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
